Christian,
The only real, relevant difference I see between the osgi:install and the features:install would be that the features:install would try to refresh other bundles that have an optional import for netty in order to get those imports wired. Could you try using a 'features:install -r netty' (no auto refresh) to check if that is really the problem here. If it is, you could try running a 'features:install -c netty' (don't clean up after failure) after setting the log level to DEBUG or TRACE to figure out what the problem bundles are. Also, you might want to try switching to felix in etc/config.properties to see if Felix manages to give you a more precise error message in this case. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Mon, Feb 7, 2011 at 1:13 PM, Christian Mueller <[email protected]> wrote: > > Hello List! > > We are using FUSE ESB 4.2.0-fuse-02-00 and providing our own features (based > on our use cases). We have a problem with one of our feature definitions. > If we run a > osgi:install -s mvn:org.jboss.netty/netty/3.1.5.GA > > everything works well. > If we create a feature which includes this bundle like the following > <feature name="netty" version="1.1.0"> > <bundle>mvn:org.jboss.netty/netty/3.1.5.GA</bundle> > </feature> > > and we run a > features:install netty > > Nothing happens. On the console, we get the following result: > features:install netty > null > > Nothing in the log file. > Does anybody have also seen this issue? Any ideas why this is happening? > > Thanks in advance, > Christian > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374147.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
