[
https://issues.apache.org/jira/browse/KARAF-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070757#comment-15070757
]
Amichai Rothman commented on KARAF-3973:
----------------------------------------
{code}
>>headers 11
myapp common [com.myapp.common] (11)
-------------------------------------------------------
Bnd-LastModified = 1450866818350
Build-Jdk = 1.8.0_66
Built-By = amichai
Created-By = Apache Maven Bundle Plugin
Manifest-Version = 1.0
Tool = Bnd-2.3.0.201405100607
Bundle-ManifestVersion = 2
Bundle-Name = myapp common [com.myapp.common]
Bundle-SymbolicName = com.myapp.common
Bundle-Version = 0.1.0.SNAPSHOT
Require-Capability =
osgi.ee;filter:=(&(osgi.ee=JavaSE)(version=1.8))
Export-Package =
com.myapp.common.core;
uses:="com.myapp.common.util,
javax.xml.bind.annotation";
version=0.1.0.SNAPSHOT,
com.myapp.common.framework;
uses:="com.myapp.common.util,
org.osgi.framework";
version=0.1.0.SNAPSHOT,
com.myapp.common.util;version=0.1.0.SNAPSHOT
Import-Package =
javax.xml.bind.annotation,
org.osgi.framework;version="[1.7,2)",
org.osgi.util.tracker;version="[1.5,2)",
org.slf4j;version="[1.7,2)"
{code}
> Bundles refresh doesn't work (bundles not resolved)
> ---------------------------------------------------
>
> Key: KARAF-3973
> URL: https://issues.apache.org/jira/browse/KARAF-3973
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.1
> Reporter: Amichai Rothman
> Priority: Critical
>
> I have a bunch of bundles copied into the deploy folder of a fresh karaf
> 4.0.1 installation. The first time karaf runs, the bundles are not properly
> resolved, and apparently this has to do with the order in which they are
> loaded, i.e. if A depends on B and A is loaded first, then when B is loaded
> it is properly resolved but A never gets resolved. running the refresh
> command from console does not help either. However, if karaf itself is
> restarted, then everything is resolved and activated with no problem.
> In Karaf up to 3.0.3 this was not an issue - the moment B was loaded, even on
> the first time Karaf is run, A would automatically get resolved/activated as
> well. on 3.0.4 I get a deadlock on startup, so can't really tell if it works
> (see KARAF-3941). on 4.0.0 I haven't tried. 4.0.1 is the current reported
> issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
