Building an Eclipse plugin using Maven

eclipse-plugin, eclipse-rcp, maven, p2, tycho

Solution

The 'org.eclipse.equinox.executable.feature.groug' seems to be necessary if you build an eclipse product which includes the native launchers ("include laucher" property set to true in product configuration). Try to add the feature to your platform definition (e.g. copy from eclipse p2 repo or your running eclipse IDE).

See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=407272

Regards, Paolo

Problem

I am trying to configure Maven to build an Eclipse application (Eclipse plugin packaged with all of the Eclipse EXEs etc). I have already Mavenised dozens of dependencies of the project and deployed them to our internal Nexus (OSS) server. I have also installed the Nexus P2 Repository Plugin and the P2 Bridge Plugin (2.6.3-01) and the Nexus Unzip Plugin (0.12.0). I can browse to the .meta/p2 folder of our group repository, but it is currently empty. This should be a lot simpler than it currently appears to be. I'm targeting Eclipse 3.4.2 (Ganymede) on Windows. If it makes any difference, we actually deploy our application packaged as a stripped-down/customised Eclipse installation. eclipse-repository When I run maven against a pom with `<packaging>eclipse-repository</packaging>` I get the following error: ``` [ERROR] Missing requirement: MyApp 0.0.0 requires 'org.eclipse.equinox.executable.feature.group 0.0.0' but it could not be found ``` ...where do I get that from, and how do I add it to Nexus? When I run maven against a pom with `<packaging>eclipse-plugin</packaging>` I get the following error: ``` [ERROR] Missing requirement: MyApp 0.0.0 requires 'bundle org.eclipse.ui 0.0.0' but it could not be found ``` ...but I found the following directories on my local file system (suspect itp-04-rcp generated the first one): ``` D:\maven\repository\p2\osgi\bundle\org.eclipse.ui\3.6.2.M20110203-1100 D:\maven\repository\p2\osgi\bundle\org.eclipse.ui\3.7.0.v20110928-1505 ``` Tycho POM-First artifacts I've also tried the pom-first-dependencies and manifest-first-dependency combo: http://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts I don't understand how this works - I can build itp02 from Git. I can see that it builds two bundles: ``` +---------------------+---------------------+--------------------------------------+ | artifactId | Bundle-Name | Bundle-SymbolicName | +---------------------+---------------------+--------------------------------------+ | pomfirst-bundle | pomfirst-bundle | tycho.demo.itp02.pomfirst-bundle | | pomfirst-thirdparty | pomfirst-thirdparty | tycho.demo.itp02.pomfirst-thirdparty | +---------------------+---------------------+--------------------------------------+ ``` ...but how does build02 pick these up? The only bit that seems relevant is: ``` Import-Package: tycho.demo.itp02.pomfirst ``` ...that doesn't have anything to do with either of the Bundle-Names. Felix Maven Bundle Plugin I tried the Felix maven-bundle-plugin. I include all of my regular maven dependencies in a pom with `<packaging>bundle</packaging>`. `mvn deploy` creates something at /nexus/content/repositories/snapshots/.meta/p2/plugins. I can download the jar via a browser, but all of the dependency jars are named "artifact-vresion" rather than "artifact_version" - is that right? `mvn bundle:bundleall` creates an OSGI bundle for each of the transitive dependencies, but I'm not sure what to do with them from here. `mvn bundle:deploy` refuses to do anything unless I specify `-DremoteOBR` and probably a few other parameters which I don't really understand.

Original source