Blueprint injection in commands

I found a really egregious bug in the config shell commands (KARAF-1140). Since writing code that gets and ungets services seems to be difficult I changed the way these work to use blueprint injection of the service rather than getting them in code (improperly). This means the commands wont b

Re: Issue with karaf-maven-plugin

There is a bug with the karaf-maven-plugin (dependency missing). I have solve it and commit code. On Thu, Jan 5, 2012 at 7:22 PM, David Jencks wrote: > It's caused by maven 3 rejecting the karaf-maven-plugin pom for > undisclosed reasons. I think it's a major bug in maven that it doesn't > stop

Re: Issue with karaf-maven-plugin

It's caused by maven 3 rejecting the karaf-maven-plugin pom for undisclosed reasons. I think it's a major bug in maven that it doesn't stop the build when it argues with something in a pom. I think rebuilding karaf usually makes it work again for a while. I think to find the alleged cause you

Issue with karaf-maven-plugin

Is it something that we already know ? [INFO] --- karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor (compile) @ --- [WARNING] The POM for org.apache.karaf.tooling:karaf-maven-plugin:jar:3.0.0-20111221.171238-221 is invalid, transitive dependencies (if any) will not be available, enab

Re: Minimal distribution

Thanks for the responses! I'll give it a shot. -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blogspot.com ** Apache Karaf Committer & PMC Apache Camel Committer Apache ServiceMix

Re: Minimal distribution

I suppose we could have a blueprint feature that would install evertyhing that is not needed by the minimal set of bundles. I think proxies are required, cm is widely used in karaf, so I doubt we can really remove it. Annotations and xbean could be installed separately. If we 're talking about the

Re: Minimal distribution

Most of these are related to having a full-featured blueprint implementation. I thought proxies were needed to make blueprint work. Something like activemq needs the blueprint namespace support and the compatibility bundle. I think regions only needs region digraph and region persistence. The

Minimal distribution

Hi all, After the talk about the size of distributions I started giving a look at the minimal distribution. An obvious change is to remove management and standard from the boot features in order to decrease the size of the distribution to 33 bundles. However, this is still a very large number of

Re: Additional JDK jars files

Thx for the clarification. On Thu, Jan 5, 2012 at 9:18 AM, Guillaume Nodet wrote: > Boot delegation controls which packages will be added to the > classloader for all bundles automatically but does not really export > the package. So if one bundle import that package, it won't be > sufficient.

Re: Additional JDK jars files

Boot delegation controls which packages will be added to the classloader for all bundles automatically but does not really export the package. So if one bundle import that package, it won't be sufficient. To export the packaes, you can use the org.osgi.framework.system.packages.extra property. If

Re: Additional JDK jars files

In config.properties, we have to modify this property --> org.osgi.framework.bootdelegation ? If jre.properties already include javax.crypto, do I have also to modify org.osgi.framework.bootdelegation property ? On Thu, Jan 5, 2012 at 8:58 AM, Guillaume Nodet wrote: > Put it in lib it will work