Hi Paul, thanks for the answer. I know these options, and once the versions of used 3rd party libs are stable, I will go for the maven bundle plugin for jars which are not available as bundles.
However, this does not completely solve our problem. There are also additonal resources which are not accessible when starting the application from Eclipse using Karaf EIK. I tried to add some subdirectory of the target folder to the bundle classpath, where things are collected for packaging the war. This is of course ugly, since I don't want to have such development hacks in the manifest. Furthermore, it works for the jars and luckily also for some Vaadin widgetset compilation, but not for other resources. Typically there is some entry in the .classpath file in the Eclipse project which handles this. Seems not to work with EIK, or I just haven't yet found the correct settings. BR, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-EIK-classpath-for-Maven-Dependencies-tp4037320p4037339.html Sent from the Karaf - User mailing list archive at Nabble.com.
