Pong ;) Andrea, could you describe the problem, why you don't like to export every single jar in the manifest? I seems to me that you are trying to resolve 3rd-party transitive dependencies and add these dynamically if you build the plugin.
2012/10/23 andrea antonello <andrea.antone...@gmail.com>: > So my final question is: do you know if there is a way to create a > plugin, that exports all the contained jars, without the need of > defining them in the manifest? Just a suggestion : Try to create a eclipse plugin from jars (new -> other -> Plug-in Development -> Plug-in from Existing jar) - select the jars you want in your bundle - on the wizard page Plug-in Project Properties you can select "unzip the JAR archives into the project" (this will create packages with extracted class files and adds all packages to the Export-Package: setting in the manifest. - no need to add jars to classpath anymore. Questions: Where are the jars from (maven dependency, manual copy task)? Do you plan to include 3rd-Party dependencies or just use the import-packages directive in the manifest.mf ? (I would prefer later, so so don't have to care about who is the "provider" of the depenencies (e.g. com.springsource.xxx , org.apache.xxx or whoever). do you have set up a branch in your github clone we can go over and check the settings? Cheers, Frank _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
