Maven on plugin RCP app -> Unable to locate feature 'org.eclipse.equinox.executable'. This feature is required for native product launchers #4443
-
I have an older Plugin based Eclipse project (non e4) that over the years has been brought along. The workspace was adapted to use a maven build a few years back where there is a main "app.build.root" project where it's pom.xml has been updated to use the Eclipse 2024-09 P2 repository and Tycho 4.0.9. App.build.root's pom also references all of the various plugins that comprise the app in addition to a app.build.product project that has just regular app.product files as <modules>. <modules> Note, there are also no *.target files in app.build.product, just the Product file generated by Eclipse. ( Also note, in the app.build.root's pom.xml flie, a plugin for "target-platform-configuration" is used with the <configuration> <enviornments> of { linux, gtk, x86_64 }, { macosx, cocoa, x86_64 }, {macosx, cocoa, aarch64 }, {win32, win32, x86_64 }. We've never got this to work on any platform, but bringing it just in case. ) In regards to the app.product file, it lists all the plugins required for the app and also has checked the "The product includes native launcher artifacts." In any case, after updating the pom.xml's to the latest libraries/versions, the maven build fails with the following: [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.9:publish-products (default-publish-products) on project app.build.product: Publisher failed. Verify your target-platform-configuration and executionEnvironment are suitable for proper resolution: Unable to locate feature 'org.eclipse.equinox.executable'. This feature is required for native product launchers. -> [Help 1]
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
A quick addendum - I know this probably has nothing to do with a tycho build because it is using the Eclipse IDE, but if I open the app.product file and click Launch as Eclipse Executable or Export it, I can generated an executable binary, so it is not believed the problem is in that file. -Jeff |
Beta Was this translation helpful? Give feedback.
-
This is usually a configuration problem so it is quite hard to tell with just some fragments of code, as you are seeing other dependency revolution problems it looks like your target configuration is somehow messed up and the build does not see the required repositories. |
Beta Was this translation helpful? Give feedback.
-
Is it the first experience you're having with Tycho? Migrating an old code base can be a tricky exercise, before starting it, make sure you've gone though a few tutorials to understand the underlying concepts and error messages; this is pre-requisite knowledge for being successful here. |
Beta Was this translation helpful? Give feedback.
-
A follow up to this problem. The pom.xml and app.product file were last build against Eclipse 2021-12, but were updated to Eclipse 2024-09. While I had updated the Eclipse p2 repository in the pom.xml file, and had let Eclipse 2024-09 make changes to app.product, I had not committed the changes to app.product's listing of required <plugins> to our version control system. Once that change was committed, the build for maven started working again. Thanks for everyone's suggestions. It was laeubi's suggestion that pointed me in the right direction. Thank you, |
Beta Was this translation helpful? Give feedback.
A follow up to this problem.
The pom.xml and app.product file were last build against Eclipse 2021-12, but were updated to Eclipse 2024-09.
While I had updated the Eclipse p2 repository in the pom.xml file, and had let Eclipse 2024-09 make changes to app.product, I had not committed the changes to app.product's listing of required <plugins> to our version control system. Once that change was committed, the build for maven started working again.
Thanks for everyone's suggestions. It was laeubi's suggestion that pointed me in the right direction.
Thank you,
-Jeff