My personal opinion is that support for wrap urls is not a good idea anywhere.
If we are going to do something to support using non-bundles as input to the kar contents I would think the way to do it is to require a complete enough wrap url to do a good job, and turn the jar into a bundle on the way into the kar. thanks david jencks On Nov 14, 2011, at 1:06 PM, mgardiner wrote: > Hi All, > > I am trying to use the karaf-maven-plugin 3.0.0-SNAPSHOT to generate a > features.xml and bundle it into the KAR but I am seeing an issue for > non-bundles. It does generate a feature xml file but what I am noticing is > that none of the urls for non-bundles in the generated feature xml get > prefixed with a "wrap:" so when I deploy the kar to the deploy directory in > Karaf 2.2.4 it throws a BundleException. > > org.osgi.framework.BundleException: Jar is not a bundle, no > Bundle-SymbolicName > > As a work-around I explicity put "wrap:" prefix in front of the uri for the > non-bundles in an input feature xml and then I end up with two bundles being > defined in the output feature.xml. I can exclude the artifact in my pom.xml > in the dependency list but this does not always work for transient > dependencies. > > So how do I > > 1) Use the karaf-maven-plugin but not overwrite my manually created > feature.xml to build a KAR > or > 2) Use the karaf-maven-plugin to build a KAR that automatically generates > the feature xml with correctly prefixed uris that include the "wrap:" prefix > for non-bundles > > Thanks. > > -Mike- > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Building-KARs-with-karaf-maven-plugin-3-0-0-SNAPSHOT-tp3507984p3507984.html > Sent from the Karaf - User mailing list archive at Nabble.com.
