I've confirmed that 

featuresBootAsynchronous=false 
felix.fileinstall.active.level = 80 

are indeed the settings that are being used. Oddly enough when I ran it
again I couldn't reproduce the error on my build environment. However when I
set up the same deployment method in a Docker container, it occurred again.
Here is the console output showing the problem:

admin@witchdoctor>bundle:list
START LEVEL 100 , List Threshold: 50
 ID | State     | Lvl | Version | Name
-----------------------------------------------------------------
 10 | Installed |  80 | 2.1.0   | Framework Library: Core
 11 | Installed |  80 | 0.1.0   | nik-hello-world
 12 | Active    |  50 | 2.6.3   | Jackson-annotations
 13 | Active    |  50 | 2.6.3   | Jackson-core
 14 | Active    |  50 | 2.6.3   | jackson-databind
 15 | Active    |  50 | 2.6.3   | Jackson-JAXRS-base
 16 | Active    |  50 | 2.6.3   | Jackson-JAXRS-JSON
 17 | Active    |  50 | 2.6.3   | Jackson-module-JAXB-annotations
 22 | Active    |  50 | 2.0.1   | javax.ws.rs-api
 37 | Active    |  50 | 2.16.3  | camel-blueprint
 38 | Active    |  50 | 2.16.3  | camel-catalog
 39 | Active    |  50 | 2.16.3  | camel-commands-core
 40 | Active    |  50 | 2.16.3  | camel-core
 41 | Active    |  50 | 2.16.3  | camel-cxf
 42 | Active    |  50 | 2.16.3  | camel-cxf-transport
 43 | Active    |  50 | 2.16.3  | camel-jackson
 44 | Active    |  50 | 2.16.3  | camel-mina2
 45 | Active    |  50 | 2.16.3  | camel-spring
 46 | Active    |  50 | 2.16.3  | camel-karaf-commands
 47 | Active    |  50 | 1.10.0  | Apache Commons Codec
 48 | Active    |  50 | 2.4.0   | Commons IO
 49 | Active    |  50 | 3.4.0   | Apache Commons Lang
 94 | Active    |  50 | 2.0.9   | Apache MINA Core
149 | Installed |  80 | 0.1     | standalone
admin@witchdoctor>bundle:diag 10
Framework Library: Core (10)
----------------------------
Status: Installed
Unsatisfied Requirements:


admin@witchdoctor>bundle:start 10
Error executing command: Error executing command on bundles:
        Error starting bundle 10: Unable to resolve fwk-lib-core [10](R 10.0):
missing requirement [fwk-lib-core [10](R 10.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.commons.codec.binary)(version>=1.10.0)(!(version>=2.0.0)))
Unresolved requirements: [[fwk-lib-core [10](R 10.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.commons.codec.binary)(version>=1.10.0)(!(version>=2.0.0)))]

-----------------------------

As you can see, bundle IDs 10 and 11 are my own jar. Bundle ID 149 is my
blueprint file. For whatever reason when I run diag on bundle 10 is doesn't
list any unsatisfied requirements, but if I try to start it is says I'm
missing my dependency on Apache Commons Codec. That bundle (ID 47) is active
and a part of the boot features we have installed. My other bundles fail to
start for similar reasons.

However if I start up my Karaf instance first and then put the two jars and
blueprint into the deploy folder, everything activates correctly with no
missing dependencies.





--
View this message in context: 
http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-tp4047948p4047953.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to