Drools repository setup on local system

[Ritvij Sharma]

Hello everyone, I am setting up the drools repository on my system https://github.com/kiegroup/drools

But while using mvn clean install -DskipTests as told in docs, I am always getting the same error (I have ran the command multiple times as said in the docs)

This is the error:-

[INFO] --- exec-maven-plugin:1.5.0:exec (generate-schema-types) @ kie-pmml ---

[ERROR] Command execution failed.

java.io.IOException: Cannot run program "${env.JAVA_HOME}/bin/java" (in directory "/home/ritvij14/Projects/drools/kie-pmml"): error=2, No such file or directory

    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1128)

    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1071)

    at java.lang.Runtime.exec (Runtime.java:592)

    at org.apache.commons.exec.launcher.Java13CommandLauncher.exec (Java13CommandLauncher.java:61)

    at org.apache.commons.exec.DefaultExecutor.launch (DefaultExecutor.java:279)

    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:336)

    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)

    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:764)

    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)

    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)

    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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    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: java.io.IOException: error=2, No such file or directory

    at java.lang.ProcessImpl.forkAndExec (Native Method)

    at java.lang.ProcessImpl.<init> (ProcessImpl.java:340)

    at java.lang.ProcessImpl.start (ProcessImpl.java:271)

    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1107)

    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1071)

    at java.lang.Runtime.exec (Runtime.java:592)

    at org.apache.commons.exec.launcher.Java13CommandLauncher.exec (Java13CommandLauncher.java:61)

    at org.apache.commons.exec.DefaultExecutor.launch (DefaultExecutor.java:279)

    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:336)

    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)

    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:764)

    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)

    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)

    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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:566)

    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)

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  8.341 s

[INFO] Finished at: 2021-01-25T13:36:06+05:30

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (generate-schema-types) on project kie-pmml: Command execution failed.: Cannot run program "${env.JAVA_HOME}/bin/java" (in directory "/home/ritvij14/Projects/drools/kie-pmml"): error=2, No such file or directory -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

The build is always failing at the same point, that is in the /drools/kie-pmml/  folder.

[Luca Molteni]

> On 25 Jan 2021, at 09:19, Ritvij Sharma <ritvi...@gmail.com> wrote:
>
> Hello everyone, I am setting up the drools repository on my system https://github.com/kiegroup/drools
>
> But while using mvn clean install -DskipTests as told in docs, I am always getting the same error (I have ran the command multiple times as said in the docs)
>
> This is the error:-
> [INFO] --- exec-maven-plugin:1.5.0:exec (generate-schema-types) @ kie-pmml ---
> [ERROR] Command execution failed.

> java.io.IOException: Cannot run program "${env.JAVA_HOME}/bin/java”

It seems like the JAVA_HOME variable is not set properly

How did you install Java?

Can you try

echo $JAVA_HOME

from a terminal?

Let us know

L.M.

[Ritvij Sharma]

Yes, thanks for the hint.
I think I made some mistakes in setting up the JAVA_HOME variable. On running that command I got no output and googled the issue and found the answer. I shifted to Linux recently so maybe I messed up while adding the JAVA_HOME variable.

Now, the build was a success. :D