You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Achim Nierbeck (JIRA)" <ji...@apache.org> on 2011/03/25 20:51:05 UTC
[jira] [Created] (KARAF-534) Startlevel: Strange deployment
behaviour
Startlevel: Strange deployment behaviour
-----------------------------------------
Key: KARAF-534
URL: https://issues.apache.org/jira/browse/KARAF-534
Project: Karaf
Issue Type: Bug
Components: runtime
Affects Versions: 2.2.1
Reporter: Achim Nierbeck
Fix For: 2.2.1
In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
Scenario:
Bundle A depends on Bundle B but Bundle B isn't deployed yet.
Deploy Bundle A by copying it to the deploy folder. The Bundle
doesn't show up when issuing the list command. If la is used
the bundle is shown in a Installed state and it is using startlevel 1.
Now if Bundle B is deployed (even by command on shell) it also
is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-534:
---------------------------------------
Affects Version/s: 3.0.0
Fix Version/s: 3.0.0
This issue is also present on the trunk.
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022640#comment-13022640 ]
Jean-Baptiste Onofré commented on KARAF-534:
--------------------------------------------
Achim succeed to reproduce the issue with the following actions:
<anierbeck> to set the version of the webconsole to 1.0.3-SNAPSHOT (it should be 1.0.2 right now)
<anierbeck> in the standard features xml
<anierbeck> in your runtime
<anierbeck> do features:install web webconsole
<anierbeck> and you'll see that webconsole failed but web is in sl 1 :)
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022057#comment-13022057 ]
Jean-Baptiste Onofré commented on KARAF-534:
--------------------------------------------
Using Karaf 2.2.1-SNAPSHOT, I tried:
karaf@root> features:install war
The level looks good:
[ 40] [Active ] [Created ] [ 30] Apache Karaf :: Deployer :: Karaf Archive (.kar) (2.2.1.SNAPSHOT)
[ 41] [Active ] [Created ] [ 30] Apache Karaf :: Shell :: ConfigAdmin Commands (2.2.1.SNAPSHOT)
[ 42] [Active ] [ ] [ 60] geronimo-servlet_2.5_spec (1.1.2)
[ 43] [Active ] [ ] [ 60] Jetty :: Utilities (7.3.1.v20110307)
[ 44] [Active ] [ ] [ 60] Jetty :: IO Utility (7.3.1.v20110307)
[ 45] [Active ] [ ] [ 60] Jetty :: Http Utility (7.3.1.v20110307)
[ 46] [Active ] [ ] [ 60] Jetty :: Asynchronous HTTP Client (7.3.1.v20110307)
[ 47] [Active ] [ ] [ 60] Jetty :: Continuation (7.3.1.v20110307)
[ 48] [Active ] [ ] [ 60] Jetty :: JMX Management (7.3.1.v20110307)
[ 49] [Active ] [ ] [ 60] Jetty :: Server Core (7.3.1.v20110307)
[ 50] [Active ] [ ] [ 60] Jetty :: Security (7.3.1.v20110307)
[ 51] [Active ] [ ] [ 60] Jetty :: Servlet Handling (7.3.1.v20110307)
[ 52] [Active ] [ ] [ 60] Jetty :: Utility Servlets and Filters (7.3.1.v20110307)
[ 53] [Active ] [ ] [ 60] Jetty :: XML utilities (7.3.1.v20110307)
[ 54] [Active ] [ ] [ 60] OPS4J Pax Web - API (1.0.2)
[ 55] [Active ] [ ] [ 60] OPS4J Pax Web - Service SPI (1.0.2)
[ 56] [Active ] [ ] [ 60] OPS4J Pax Web - Runtime (1.0.2)
[ 57] [Active ] [ ] [ 60] OPS4J Pax Web - Jetty (1.0.2)
[ 58] [Active ] [ ] [ 60] JavaMail API (1.4.3)
[ 59] [Active ] [ ] [ 60] geronimo-jta_1.1_spec (1.1.1)
[ 60] [Active ] [ ] [ 60] Jetty :: Webapp Application Support (7.3.1.v20110307)
[ 61] [Active ] [ ] [ 60] Jetty :: JNDI Naming (7.3.1.v20110307)
[ 62] [Active ] [ ] [ 60] Jetty :: Plus (7.3.1.v20110307)
[ 63] [Active ] [Created ] [ 30] Apache Karaf :: Shell :: Web Commands (2.2.1.SNAPSHOT)
[ 64] [Active ] [ ] [ 60] OPS4J Pax Web - Jsp Support (1.0.2)
[ 65] [Active ] [ ] [ 60] OPS4J Pax Web - Extender - WAR (1.0.2)
[ 66] [Active ] [ ] [ 60] OPS4J Pax Web - Extender - Whiteboard (1.0.2)
[ 67] [Active ] [ ] [ 60] OPS4J Pax Web - FileInstall Deployer (1.0.2)
[ 68] [Active ] [ ] [ 60] OPS4J Pax Url - war (1.2.6)
I make some new tries.
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021492#comment-13021492 ]
Jean-Baptiste Onofré commented on KARAF-534:
--------------------------------------------
This issue looks related to Felix framework and it still presents on the Karaf trunk.
I'm gonna make a try using the latest Felix framework version (including snapshot/stage).
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020024#comment-13020024 ]
Achim Nierbeck commented on KARAF-534:
--------------------------------------
This seems to be only related to felix as underlying osgi container, if equinox is used it runs fine.
A easier test can be achieved by
{code}
features:install war
{code}
after that all the bundles besides one are set to level 1
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-534:
---------------------------------
Priority: Critical (was: Major)
Increasing priority level.
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved KARAF-534.
-----------------------------------
Resolution: Fixed
Assignee: Guillaume Nodet
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Assignee: Guillaume Nodet
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KARAF-534) Startlevel: Strange deployment
behaviour
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-534.
--------------------------------
Fixed in the 2.2.1 release.
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Assignee: Guillaume Nodet
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira