Konrad Windszus created SLING-10416:
---------------------------------------
Summary: feature-launcher-maven-plugin:start does not work with m2e
Key: SLING-10416
URL: https://issues.apache.org/jira/browse/SLING-10416
Project: Sling
Issue Type: Improvement
Components: Feature Model, Tooling
Affects Versions: Feature Launcher Maven Plugin 0.1.0
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Fix For: Feature Launcher Maven Plugin 0.1.2
When trying to execute {{feature-launcher-maven-plugin:start}} from within
Eclipse (with the embedded Maven runtime used in m2e) I run into the following
exception:
{code}
[ERROR] Failed to execute goal
org.apache.sling:feature-launcher-maven-plugin:0.1.0:start (default) on project
org.apache.sling.starter: Cannot run program "null/bin/java" (in directory
"/Users/konradwindszus/git/sling/sling-org-apache-sling-starter/target/launchers"):
error=2, No such file or directory -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.sling:feature-launcher-maven-plugin:0.1.0:start (default) on project
org.apache.sling.starter: Cannot run program "null/bin/java" (in directory
"/Users/konradwindszus/git/sling/sling-org-apache-sling-starter/target/launchers"):
error=2, No such file or directory
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot run program
"null/bin/java" (in directory
"/Users/konradwindszus/git/sling/sling-org-apache-sling-starter/target/launchers"):
error=2, No such file or directory
at
org.apache.sling.maven.feature.launcher.StartMojo.execute(StartMojo.java:174)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
... 20 more
Caused by: java.io.IOException: Cannot run program "null/bin/java" (in
directory
"/Users/konradwindszus/git/sling/sling-org-apache-sling-starter/target/launchers"):
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at
org.apache.sling.maven.feature.launcher.StartMojo.execute(StartMojo.java:142)
... 22 more
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 23 more
{code}
Determining JAVA_HOME should be more resilient to be able to deal with that
case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
