Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Error: Tycho unable to locate the equinox launcher feature

Sorry, want to follow up a little bit more as I have some additional information on the issue.

That stack trace only occurs if I check the 'The product includes native launcher artifacts' checkbox in the *Product Editor in Eclipse.  

However, if I leave that checkbox unchecked, the resulting product archives do NOT contain an executable to launch the resultant application.  Additionally, while I am specifying a launcher name of 'xxx' in the 'Launching' section of the *Product Editor, I see it is creating a 'eclipse.ini' file.  It is my understanding that this ini file should match the launcher name.

I saw this type of behavior before in PDE when it could not locate the org.eclipse.equinox.executable feature - so it might just be a different manifestation of the same problem.



On Wed, Dec 17, 2014 at 10:47 AM, Andy Stoneberg <stonebaj@xxxxxxxxx> wrote:
Greetings again.  I am moving from a PDE/Ant based build into Tycho - so probably more questions will be forthcoming :)  

Most of the conversion has been amazingly easy and understandable ( nice change from the mess that is PDE ).  However, I am now encountering issues when trying to execute the tycho-p2-publisher-plugin:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.21.0:publish-products (default-publish-products) on project Unable to locate the equinox launcher feature (aka delta-pack) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.21.0:publish-products (default-publish-products) on project Unable to locate the equinox launcher feature (aka delta-pack)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
at org.apache.maven.DefaultMaven.doExecute(
at org.apache.maven.DefaultMaven.execute(
at org.apache.maven.cli.MavenCli.execute(
at org.apache.maven.cli.MavenCli.doMain(
at org.apache.maven.cli.MavenCli.main(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
at org.codehaus.plexus.classworlds.launcher.Launcher.main(
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to locate the equinox launcher feature (aka delta-pack)
at org.eclipse.tycho.plugins.p2.publisher.PublishProductMojo.getEquinoxExecutableFeature(
at org.eclipse.tycho.plugins.p2.publisher.PublishProductMojo.publishContent(
at org.eclipse.tycho.plugins.p2.publisher.AbstractPublishMojo.execute(
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
... 19 more

Now, I am not necessarily surprised by this error but need/want to understand how Tycho expects to resolve this dependency.  The product I am building is based on a subset of Eclipse features/plugins - so when our clients point to our P2 repository, they get everything they need/can use from a single P2 repo (aka - they aren't pointing to "my" P2 repo + standard Eclipse repo).  I am packaging the org.eclipse.equinox.executable feature in my P2 repository with our relevant/supported O/S fragments. I can see the launcher fragments & root IUs are downloaded in my Maven repository (under the p2  /osgi/bundle & /binary folders respectively).  However, the org.eclipse.equinox.executable feature itself is NOT present in org/eclipse/update/feature directory.  I'm guessing it is because the feature is not listed *product file describing the build.  However, as this is really only a build-time dependency, I would prefer to not add it here.

Any help/insight would be appreciated.  Also, if I am rambling and not making sense - let me know and I will happily address any further questions about my setup.


Back to the top