

I think the syntax to create these files using the plugin is quite verbose and rather use the PDE tools for generating a bundle. (4) Add a plugin to configure the bundles manifest file. (1) bundle must be added (2) A plugin to copy the dependencies must be added (I added a further execution to unpack the dependencies for reasons described in OSGi: Libraries Requiring Access to Bundle ClassLoader) maven-dependency-plugin unpack-dependencies generate-resources unpack-dependencies org.swinglabs,org.jdesktop,com.sun copy-dependencies process-sources copy-dependencies $ \*.jar false This must be configured in the project‘s pom.xml file. The dependencies are the jars in the following screenshot. The Maven dependencies are directly copied to the project‘s main folder. I found that this procedure works fine with eclipse projects, which are already linked to eclipse IAM and have been created as eclipse plugin projects. It does so by copying the JARs that the Maven project depends on and by altering the. This Maven plugin is able to generate the necessary files for the eclipse PDE to work with the Maven files. I have already written about some necessary tweaks to get it working.Īnother way is to use the Apache Felix Maven bundle plugin.

To get eclipse PDE working hand in hand with Maven is a rather tricky task.
