I have a number of features which I'm bundling as .kar files so that the bundles will ship with them. It seems whenever I have a bundle with dependency='true" on it, the create-kar goal does not put the bundle into the kar repository.
I understood that dependency='true' indicates that this is a shared dependency.. if it is already installed in the container, do not reinstall it (in fact I'm not certain when you would NOT want that behavior). Is it intentional that create-kar is not putting the bundle into the archive when it is marked as a dependency, and what is the logic there? It might be that I misunderstand the purpose of the dependency attribute. Thanks. - Tim Stewart. -- View this message in context: http://karaf.922171.n3.nabble.com/create-kar-plugin-with-dependency-bundles-tp4030364.html Sent from the Karaf - User mailing list archive at Nabble.com.
