Christian, We're expecting the META-INF/MANIFEST.MF to be the first entry of the JAR - not sure if that's part of any specification, but all the JAR tooling (jar command line tool, Ant, Buildr, Maven, ...) seems to behave that way anyway. One of the benefits is that you don't have to read through an entire archive to get to the metadata, mostly important for larger JAR files or things being downloaded over the network. The FeaturesService uses the metadata to determine whether or not the bundle listed in the feature is actually installed and can be skipped. Looks like the OSGi framework itself does not depend on that behavior, that's why a plain osgi:install works fine.
This issue is fixed in more recent versions of Netty (https://issues.jboss.org/browse/NETTY-376), for the 3.2.3.Final version we did our own bundle release to fix this issue. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Mon, Feb 7, 2011 at 6:58 PM, Christian Mueller <[email protected]> wrote: > > We use the official JBoss Netty artifact from > http://repository.jboss.org/nexus/content/groups/public/ > We can try to build our own/correct OSGI bundle with the > maven-bundle-plugin. But it looks strange for me, that osgi:install runs > without a problem and wrapping only this bundle into a features fails by > running features:install. I think both should run with success or both > should fail... > > Christian > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374677.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
