Been scratching my head at this one all day: I just updated our Karaf version from 3.0.0.RC1 to 3.0.0 today, and all of our integration tests are failing due to boot features not installing. Has anything big changed between RC1 and final that would affect boot feature configuration? If I make no changes except setting the version back to 3.0.0.RC1, it works perfectly.
During tests I use the maven karaf-assembly packaging goal to build out a Karaf app layout from the 3.0.0 bundles. It starts up as usual and installs the features.xml I provide it for the test, but It turns out that none of the boot features are being activated, so SCR does not activate my components. Nor can I connect to the console to investigate further what's going on, because the shell/SSH are not active. The following messages are showing up in my karaf.log: INFO | Bundle org.apache.karaf.shell.commands is waiting for namespace handlers INFO | Bundle org.apache.karaf.features.command is waiting for namespace handlers INFO | Bundle org.apache.karaf.system.command is waiting for namespace handlers INFO | Bundle org.apache.karaf.shell.help is waiting for dependencies [(objectClass=org.apache.felix.service.threadio.ThreadIO)] INFO | Bundle org.apache.karaf.bundle.command is waiting for namespace handlers [http://karaf.apache.org/xmlns/shell/v1.1.0] INFO | Bundle org.apache.karaf.shell.console is waiting for dependencies [(objectClass=org.apache.felix.service.command.CommandProcessor), (objectClass=org.apache.felix.service.threadio.ThreadIO)] Googling has linked this to machines without an internet connection, which is not the case here. My etc/org.apache.karaf.features.cfg: featuresRepositories=mvn:org.apache.karaf.features/standard/3.0.0/xml/features,mvn:org.apache.karaf.features/enterprise/3.0.0/xml/features,mvn:org.ops4j.pax.web/pax-web-features/3.0.5/xml/features,mvn:org.apache.karaf.features/spring/3.0.0/xml/features featuresBoot=config,standard,region,package,kar,ssh,management,eventadmin,scr featuresBootAsynchronous=false
