Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Scout » Cannot build project
Cannot build project [message #1830644] Thu, 30 July 2020 11:42 Go to next message
Mr Robot is currently offline Mr RobotFriend
Messages: 72
Registered: March 2020
Member
Hi,

I created new Scout 10 project using latest Eclipse. I have Node installed.

I can run app localy. But problem is when I try to build .war files. It gets failed on UI.HTML project.

I use clean verify command on main project.

This is error:
Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project

Tried this 10 times already, but no luck.

Before I could create new project, but now I cant.

This is error with maven -X command:
 Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project testproject.ui.html: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project testproject.ui.html: Command execution failed.
	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: Command execution failed.
	at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:326)
	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: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
	at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
	at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
	at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
	at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
	... 22 more
[ERROR] 
[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
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :testproject.ui.html

Report message to a moderator

Re: Cannot build project [message #1830645 is a reply to message #1830644] Thu, 30 July 2020 11:48 Go to previous messageGo to next message
Mr Robot is currently offline Mr RobotFriend
Messages: 72
Registered: March 2020
Member
 
internal/modules/cjs/loader.js:797
    throw err;
    ^

Error: Cannot find module 'C:\test\workspace\testproject\testproject\target\node\node_modules\@eclipse-scout\releng\bin\releng-scripts.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:794:15)
    at Function.Module._load (internal/modules/cjs/loader.js:687:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
    at internal/main/run_main_module.js:17:11 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
	at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
	at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
	at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
	at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
	at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
	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 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)
[INFO] ------------------------------------------------------------------------

Report message to a moderator

Re: Cannot build project [message #1830680 is a reply to message #1830644] Fri, 31 July 2020 06:14 Go to previous messageGo to next message
Senaka Suriyaarachchi is currently offline Senaka SuriyaarachchiFriend
Messages: 14
Registered: July 2020
Junior Member
Hi
Did you resolve your problem? I am facing same kind of issue when try to build war file.

If you resolved the above issue please advice me.

Regards
Senaka

Report message to a moderator

Re: Cannot build project [message #1830692 is a reply to message #1830680] Fri, 31 July 2020 15:01 Go to previous messageGo to next message
Mr Robot is currently offline Mr RobotFriend
Messages: 72
Registered: March 2020
Member
No I didn't. I think it is Node related issue. Permission problem or something

Report message to a moderator

Re: Cannot build project [message #1830862 is a reply to message #1830692] Wed, 05 August 2020 11:55 Go to previous messageGo to next message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
Hello

@MrRobot: could you check if the module "@eclipse-scout/releng" exists in your node_modules directory here?

C:\test\workspace\testproject\testproject\target\node\node_modules

Please also check if that module is defined as devDependency in the package.json of the "testproject.ui.html" module.

Maybe you could also attach your package.json to your reply.

Please also provide the output from these two commands:
node --version
java -version

When I run "mvn clean verify" my output for that goal that fails in your case looks like this. How does your output look like? (before the failure occurs):

[INFO] --- exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) @ testproject.ui.html ---
unable to find workspace file. Use parent directory as workspace root: C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\testproject\
start searching for package.json files at C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\testproject\
updating version/dependency for module: @testproject/ui
setPreInstallSnapshotDependencies version done

Cheers,
André

Eclipse Scout Homepage | Documentation | GitHub

[Updated on: Wed, 05 August 2020 12:48]

Report message to a moderator

Re: Cannot build project [message #1830890 is a reply to message #1830862] Thu, 06 August 2020 04:16 Go to previous messageGo to next message
Senaka Suriyaarachchi is currently offline Senaka SuriyaarachchiFriend
Messages: 14
Registered: July 2020
Junior Member
Hi Andre,
I also experienced same issue.
I couldn't fine the module "@eclipse-scout/releng" in my node_modules directory in the following location.
E:\senaka\eclipseworkspace\helloworld\helloworld\target\node\node_modules
In this directory has npm sub directory only.

I have checked the package.json file and" @eclipse-scout/releng" devDependency is there.
devDependencies": {
"@eclipse-scout/cli": "10.0.21",
"@eclipse-scout/testing": "10.0.21",
"@eclipse-scout/releng": "^10.0.0",
"@eclipse-scout/eslint-config": "10.0.21",
"eslint": "6.5.1",
"babel-eslint": "10.0.3",
"eslint-plugin-babel": "5.3.0"
},
I have attached package.json file for your reference.

Please check following for my node and java versions.
node --version
v12.16.1

npm --version
6.13.4

pnpm --version
4.13.0


java -version
openjdk version "11" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

Regards
Senaka
  • Attachment: package.json
    (Size: 1.36KB, Downloaded 98 times)

Report message to a moderator

Re: Cannot build project [message #1830894 is a reply to message #1830890] Thu, 06 August 2020 06:43 Go to previous messageGo to next message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
Thanks Senaka. Package.json looks alright. There's a lot going on in our maven build, it triggers the NPM build too. So I guess the problem lies there somewhere.
Could you please attach the full log of your Maven build here? I guess the easiest way is to run maven on the command line:

mvn clean verify > C:\temp\helloworld-maven.log

Or in the Eclipse IDE: change the preferences of the Console and un-check the "Limit console output" check-box, before your run the maven build.

Eclipse Scout Homepage | Documentation | GitHub

Report message to a moderator

Re: Cannot build project [message #1830897 is a reply to message #1830894] Thu, 06 August 2020 08:04 Go to previous messageGo to next message
Claudio Guglielmo is currently offline Claudio GuglielmoFriend
Messages: 259
Registered: March 2010
Senior Member
If there is no @eclipse-scout or pnpm directory in the target/node_modules folder, than the task "install-node-tools" probably failed or has been skipped.
This should be visible in the log as André suggested. I get the following output:

[INFO] --- frontend-maven-plugin:1.9.1:install-node-and-npm (install-node-and-npm) @ helloworld.ui.html ---
[INFO] Installing node version v12.12.0
[INFO] Unpacking C:\Users\cgu\.m2\repository\com\github\eirslett\node\12.12.0\node-12.12.0-win-x64.zip into C:\dev\temp\arche\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\tmp
[INFO] Copying node binary from C:\dev\temp\arche\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\tmp\node-v12.12.0-win-x64\node.exe to C:\dev\temp\arche\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\node.exe
[INFO] Installed node locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.9.1:npm (install-node-tools) @ helloworld.ui.html ---
[INFO] Running 'npm install -g pnpm@4.13.0 @eclipse-scout/releng@^10.0.0' in C:\dev\temp\arche\helloworld\helloworld.ui.html
[INFO] C:\dev\temp\arche\helloworld\helloworld\target\node\releng-scripts -> C:\dev\temp\arche\helloworld\helloworld\target\node\node_modules\@eclipse-scout\releng\bin\releng-scripts.js
[INFO] C:\dev\temp\arche\helloworld\helloworld\target\node\pnpm -> C:\dev\temp\arche\helloworld\helloworld\target\node\node_modules\pnpm\bin\pnpm.js
[INFO] C:\dev\temp\arche\helloworld\helloworld\target\node\pnpx -> C:\dev\temp\arche\helloworld\helloworld\target\node\node_modules\pnpm\bin\pnpx.js
[INFO] + @eclipse-scout/releng@10.0.3
[INFO] + pnpm@4.13.0
[INFO] added 181 packages from 101 contributors in 13.646s

Maybe also delete the node_modules folder in the ui.html module first. If you use another package manager than the maven build (e.g. npm) conflicts can arise, because pnpm will move the installed modules to a general store and link them. If you run npm install again afterwards it probably cannot handle it.
I don't think this is likely your problem, but maybe you will run into it later on....

Report message to a moderator

Re: Cannot build project [message #1830901 is a reply to message #1830894] Thu, 06 August 2020 09:56 Go to previous messageGo to next message
Senaka Suriyaarachchi is currently offline Senaka SuriyaarachchiFriend
Messages: 14
Registered: July 2020
Junior Member
Hi,
Please check the attached log file for clean verify build.

Regards
Senaka

Report message to a moderator

Re: Cannot build project [message #1830905 is a reply to message #1830901] Thu, 06 August 2020 11:26 Go to previous messageGo to next message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
Thanks again! I found the following error in your build log:

[INFO] Running 'npm install -g pnpm@4.13.0 @eclipse-scout/releng@^10.0.0' in E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html
[INFO] npm ERR! code E404
[INFO] npm ERR! 404 Not Found - GET https://registry.npmjs.org/@pnpm%2ffind-workspace-packages - Not found

Currently npmjs.org has some serious issues going on, See:
https://status.npmjs.org/

I guess that's the reason why npm cannot resolve the module on your machine (I experienced similar problems while I was analyzing the problems reported here).
I'm afraid we cannot do a lot until npmjs.org has solved its problems :-( When npmjs.org is alive again, we should run your build again and check if something has changed.

Cheers,
André

Eclipse Scout Homepage | Documentation | GitHub

Report message to a moderator

Re: Cannot build project [message #1830946 is a reply to message #1830905] Fri, 07 August 2020 07:36 Go to previous messageGo to next message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
Hi Senaka

Npmjs.org has fixed its problems yesterday. Could you please run the maven build and attach the .log file again?

Thank you
André

Eclipse Scout Homepage | Documentation | GitHub

Report message to a moderator

Re: Cannot build project [message #1830951 is a reply to message #1830946] Fri, 07 August 2020 08:31 Go to previous messageGo to next message
Senaka Suriyaarachchi is currently offline Senaka SuriyaarachchiFriend
Messages: 14
Registered: July 2020
Junior Member
Hi Andre,
Thank you for the notify me.
Please check the attached log file.
I just included the following extract from the log file as well.
[DEBUG] env: USERPROFILE=C:\Users\mathe
[DEBUG] env: WINDIR=C:\WINDOWS
[DEBUG] Executing command line: [E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\..\helloworld\target\node\node, E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\../helloworld\target\node/node_modules/@eclipse-scout/releng/bin/releng-scripts.js, snapshot-install-dependency]
internal/modules/cjs/loader.js:797
throw err;
^

Error: Cannot find module 'E:\senaka\eclipseworkspace\helloworld\helloworld\target\node\node_modules\@eclipse-scout\releng\bin\releng-scripts.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:794:15)
at Function.Module._load (internal/modules/cjs/loader.js:687:27)
at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
at internal/main/run_main_module.js:17:11 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/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] Reactor Summary for My Application Parent Module 1.0.0-SNAPSHOT:
[INFO]
[INFO] My Application Parent Module ....................... SUCCESS [ 18.940 s]
[INFO] My Application Shared .............................. SUCCESS [ 24.390 s]
[INFO] My Application Server .............................. SUCCESS [ 31.759 s]
[INFO] My Application Client .............................. SUCCESS [ 30.634 s]
[INFO] My Application Server Application .................. SUCCESS [ 11.099 s]
[INFO] My Application HTML UI ............................. FAILURE [01:41 min]
[INFO] My Application HTML UI Application ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:39 min
[INFO] Finished at: 2020-08-07T13:54:45+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project helloworld.ui.html: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project helloworld.ui.html: Command execution failed.
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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/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: org.apache.maven.plugin.MojoExecutionException: Command execution failed.
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:326)
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: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
... 22 more
[ERROR]
[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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :helloworld.ui.html

Regards
Senaka

Report message to a moderator

Re: Cannot build project [message #1830964 is a reply to message #1830951] Fri, 07 August 2020 12:36 Go to previous messageGo to next message
Mr Robot is currently offline Mr RobotFriend
Messages: 72
Registered: March 2020
Member
Senaka Suriyaarachchi wrote on Fri, 07 August 2020 08:31
Hi Andre,
Thank you for the notify me.
Please check the attached log file.
I just included the following extract from the log file as well.
[DEBUG] env: USERPROFILE=C:\Users\mathe
[DEBUG] env: WINDIR=C:\WINDOWS
[DEBUG] Executing command line: [E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\..\helloworld\target\node\node, E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\../helloworld\target\node/node_modules/@eclipse-scout/releng/bin/releng-scripts.js, snapshot-install-dependency]
internal/modules/cjs/loader.js:797
throw err;
^

Error: Cannot find module 'E:\senaka\eclipseworkspace\helloworld\helloworld\target\node\node_modules\@eclipse-scout\releng\bin\releng-scripts.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:794:15)
at Function.Module._load (internal/modules/cjs/loader.js:687:27)
at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
at internal/main/run_main_module.js:17:11 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/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] Reactor Summary for My Application Parent Module 1.0.0-SNAPSHOT:
[INFO]
[INFO] My Application Parent Module ....................... SUCCESS [ 18.940 s]
[INFO] My Application Shared .............................. SUCCESS [ 24.390 s]
[INFO] My Application Server .............................. SUCCESS [ 31.759 s]
[INFO] My Application Client .............................. SUCCESS [ 30.634 s]
[INFO] My Application Server Application .................. SUCCESS [ 11.099 s]
[INFO] My Application HTML UI ............................. FAILURE [01:41 min]
[INFO] My Application HTML UI Application ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:39 min
[INFO] Finished at: 2020-08-07T13:54:45+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project helloworld.ui.html: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (scout-releng-snapshot-install-dependency) on project helloworld.ui.html: Command execution failed.
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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/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: org.apache.maven.plugin.MojoExecutionException: Command execution failed.
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:326)
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: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:313)
... 22 more
[ERROR]
[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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :helloworld.ui.html

Regards
Senaka

I have same error with clean install of new project. Without any modifications. Created new project -> run WebAll -> build using clean verify

Report message to a moderator

Re: Cannot build project [message #1830972 is a reply to message #1830951] Fri, 07 August 2020 14:06 Go to previous messageGo to next message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
Hi Senaka

Thanks again for posting your build log here. We've analyzed your log and I compared it against my own build log. I found this difference:

[Your Log]
[INFO] Running 'npm install -g pnpm@4.13.0 @eclipse-scout/releng@^10.0.0' in E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html
[DEBUG] Executing command line [E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\node.exe, E:\senaka\eclipseworkspace\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\node_modules\npm\bin\npm-cli.js, install, -g, pnpm@4.13.0, @eclipse-scout/releng@^10.0.0]
[INFO] C:\Users\mathe\AppData\Roaming\npm\releng-scripts -> C:\Users\mathe\AppData\Roaming\npm\node_modules\@eclipse-scout\releng\bin\releng-scripts.js
[INFO] C:\Users\mathe\AppData\Roaming\npm\pnpm -> C:\Users\mathe\AppData\Roaming\npm\node_modules\pnpm\bin\pnpm.js
[INFO] C:\Users\mathe\AppData\Roaming\npm\pnpx -> C:\Users\mathe\AppData\Roaming\npm\node_modules\pnpm\bin\pnpx.js
[INFO] + pnpm@4.13.0
[INFO] + @eclipse-scout/releng@10.0.3
[INFO] updated 2 packages in 60.155s


[My Log]
[INFO] Running 'npm install -g pnpm@4.13.0 @eclipse-scout/releng@^10.0.0' in C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld.ui.html
[DEBUG] Executing command line [C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\node.exe, C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld.ui.html\..\helloworld\target\node\..\node\node_modules\npm\bin\npm-cli.js, install, -g, pnpm@4.13.0, @eclipse-scout/releng@^10.0.0]
[INFO] C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\releng-scripts -> C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\node_modules\@eclipse-scout\releng\bin\releng-scripts.js
[INFO] C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\pnpm -> C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\node_modules\pnpm\bin\pnpm.js
[INFO] C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\pnpx -> C:\Temp\eclipse-scout-2020-06-R-win32-x86_64\workspaces\helloworld\helloworld\target\node\node_modules\pnpm\bin\pnpx.js
[INFO] + pnpm@4.13.0
[INFO] + @eclipse-scout/releng@10.0.3
[INFO] added 181 packages from 101 contributors in 43.276s


In your case the two modules @eclipse-scout/releng and pnpm are installed in C:\Users\mathe\AppData\Roaming\npm, but the build expects them to be installed under the workspace/helloworld/ directory. I guess this has something to do with how you've installed NPM. I will open a Bugzilla bug for this: the build must work independent from how exactly one has installed NPM. See: Bug 565896 - Maven build fails because NPM modules are installed at the wrong location.

Could you please check if there is a NODE_PATH environment variable set on your machine?

As a workaround you could try to manually copy all files from "C:\Users\mathe\AppData\Roaming\npm\node_modules\@eclipse-scout" to "E:\senaka\eclipseworkspace\helloworld\helloworld\target\node\node_modules\@eclipse-scout" where the build expects these files. And run the build again without "clean", otherwise the directory will be deleted again.

You could also try to change the NODE_PATH variable and point it to the directory "E:\senaka\eclipseworkspace\helloworld\helloworld\target\node\node_modules" before you run the build (untested).

Hope that helps. Cheers,
André

Eclipse Scout Homepage | Documentation | GitHub

[Updated on: Fri, 07 August 2020 14:39]

Report message to a moderator

Re: Cannot build project [message #1830975 is a reply to message #1830972] Fri, 07 August 2020 14:55 Go to previous messageGo to next message
Senaka Suriyaarachchi is currently offline Senaka SuriyaarachchiFriend
Messages: 14
Registered: July 2020
Junior Member
Hi Andre,
Thank you for your detail instruction. As your instruction, I manually copied @eclipse-scout folder and it work
It works nicely!!!
[INFO] My Application Parent Module ....................... SUCCESS [ 13.196 s]
[INFO] My Application Shared .............................. SUCCESS [ 12.203 s]
[INFO] My Application Server .............................. SUCCESS [ 17.322 s]
[INFO] My Application Client .............................. SUCCESS [ 14.262 s]
[INFO] My Application Server Application .................. SUCCESS [ 3.944 s]
[INFO] My Application HTML UI ............................. SUCCESS [05:28 min]
[INFO] My Application HTML UI Application ................. SUCCESS [ 3.568 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS




Thank you again guide be to resolve this issue.

Regards
Senaka

Report message to a moderator

Re: Cannot build project [message #1835126 is a reply to message #1830975] Wed, 25 November 2020 09:33 Go to previous message
Andre Wegmueller is currently offline Andre WegmuellerFriend
Messages: 204
Registered: September 2012
Location: Baden-Dättwil, Switzerla...
Senior Member
This bug has been fixed in the Scout Maven Master. Details:
https://git.eclipse.org/c/scout/maven-master.git/commit/?id=f3d4c0796c48cc5906ef0e59a966afe60e940eab

The fix is available with maven_rt_plugin_config-master >= 3.12.8-SNAPSHOT.

Eclipse Scout Homepage | Documentation | GitHub

Report message to a moderator

Previous Topic:Scout app multi deployment - differents options ?
Next Topic:Table built-in checkable column vs. export form data
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Jan 03 03:35:44 GMT 2025

Powered by FUDForum. Page generated in 0.05058 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly