" [INFO] Binary found at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\node-sass\vendor\win32-x64-64\binding.node [INFO] Testing binary [INFO] Binary is fine [WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fseven"
I am following this tuturial :
https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-setup.html?lang=en#build
[INFO] Binary found at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\node-sass\vendor\win32-x64-64\binding.node
[INFO] Testing binary
[INFO] Binary is fine
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.3.1 (node_modules\chokidar\node_modules\fsevents):
[INFO] added 1150 packages from 604 contributors in 126.591s
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[ERROR]
[INFO]
[INFO] --- frontend-maven-plugin:1.7.6:npm (npm run prod) # aem-guides-wknd.ui.frontend ---
[INFO] Running 'npm run prod' in C:\Users\musal\code\aem-guides-wknd\ui.frontend
[INFO]
[INFO] > aem-maven-archetype#1.0.0 prod C:\Users\musal\code\aem-guides-wknd\ui.frontend
[INFO] > webpack -p --config ./webpack.prod.js && clientlib --verbose
[INFO]
[INFO] Hash: ffc73eaa92aecbde036f
[INFO] Version: webpack 4.46.0
[INFO] Time: 6708ms
[INFO] Built at: 03/18/2021 1:14:42 AM
[INFO] 1 asset
[INFO] Entrypoint site = clientlib-site/site.js
[INFO]
[INFO] WARNING in ./src/main/webpack/site/main.ts
[INFO] Module Warning (from (webpack)-import-glob-loader/index.js):
[INFO] (Emitted value instead of an instance of Error) Empty results for "import "./**/*.js""
[INFO] NonErrorEmittedError: (Emitted value instead of an instance of Error) Empty results for "import "./**/*.js""
[INFO] at Object.emitWarning (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\webpack\lib\NormalModule.js:160:16)
[INFO] at replacer (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\webpack-import-glob-loader\index.js:85:12)
[INFO] at String.replace (<anonymous>)
[INFO] at Object.module.exports (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\webpack-import-glob-loader\index.js:91:20)
[INFO]
[INFO] ERROR in ./src/main/webpack/site/main.scss
[INFO] Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
[INFO] ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/src/index.js):
[INFO] BrowserslistError: C:\Users\musal\code\aem-guides-wknd\ui.frontend contains both browserslist and package.json with browsers
[INFO] at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\browserslist\node.js:329:15
[INFO] at eachParent (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\browserslist\node.js:49:18)
[INFO] at Object.findConfig (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\browserslist\node.js:305:20)
[INFO] at Function.loadConfig (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\browserslist\node.js:223:37)
[INFO] at browserslist (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\browserslist\index.js:411:31)
[INFO] at Browsers.parse (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\autoprefixer\lib\browsers.js:63:12)
[INFO] at new Browsers (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\autoprefixer\lib\browsers.js:46:26)
[INFO] at loadPrefixes (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\autoprefixer\lib\autoprefixer.js:98:20)
[INFO] at plugin (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\autoprefixer\lib\autoprefixer.js:109:20)
[ERROR] npm ERR! code ELIFECYCLE
[INFO] at LazyResult.run (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss\lib\lazy-result.js:288:14)
[ERROR] npm ERR! errno 2
[ERROR] npm ERR! aem-maven-archetype#1.0.0 prod: `webpack -p --config ./webpack.prod.js && clientlib --verbose`
[INFO] at LazyResult.asyncTick (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss\lib\lazy-result.js:212:26)
[ERROR] npm ERR! Exit status 2
[INFO] at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss\lib\lazy-result.js:254:14
[ERROR] npm ERR!
[INFO] at new Promise (<anonymous>)
[ERROR] npm ERR! Failed at the aem-maven-archetype#1.0.0 prod script.
[INFO] at LazyResult.async (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss\lib\lazy-result.js:250:23)
[ERROR] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[INFO] at LazyResult.then (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss\lib\lazy-result.js:131:17)
[ERROR]
[INFO] at Promise.resolve.then.then (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss-loader\src\index.js:142:8)
[ERROR] npm ERR! A complete log of this run can be found in:
[INFO] at runLoaders (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\webpack\lib\NormalModule.js:316:20)
[ERROR] npm ERR! C:\Users\musal\AppData\Roaming\npm-cache\_logs\2021-03-18T06_14_42_492Z-debug.log
[INFO] at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\loader-runner\lib\LoaderRunner.js:367:11
[INFO] at C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\loader-runner\lib\LoaderRunner.js:233:18
[INFO] at context.callback (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
[INFO] at Promise.resolve.then.then.catch (C:\Users\musal\code\aem-guides-wknd\ui.frontend\node_modules\postcss-loader\src\index.js:208:9)
[INFO] # ./src/main/webpack/site/main.ts 1:0-21
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for aem-guides-wknd 0.0.1-SNAPSHOT:
[INFO]
[INFO] aem-guides-wknd .................................... SUCCESS [ 10.794 s]
[INFO] WKND Sites Project - Core .......................... SUCCESS [02:21 min]
[INFO] WKND Sites Project - UI Frontend ................... FAILURE [03:17 min]
[INFO] WKND Sites Project - Repository Structure Package .. SKIPPED
[INFO] WKND Sites Project - UI apps ....................... SKIPPED
[INFO] WKND Sites Project - UI content .................... SKIPPED
[INFO] WKND Sites Project - UI config ..................... SKIPPED
[INFO] WKND Sites Project - All ........................... SKIPPED
[INFO] WKND Sites Project - Integration Tests ............. SKIPPED
[INFO] WKND Sites Project - Dispatcher .................... SKIPPED
[INFO] WKND Sites Project - UI Tests ...................... SKIPPED
[INFO] WKND Sites Project - Project Analyser .............. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:06 min
[INFO] Finished at: 2021-03-18T01:14:42-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.7.6:npm (npm run prod) on project aem-guides-wknd.ui.frontend: Failed to run task: 'npm run prod' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 2 (Exit value: 2) -> [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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :aem-guides-wknd.ui.frontend
Looks like you could get this error for 2 main reasons:
Your npm modules are old and outdated:
Solution : Clear the node_modules and then try npm install again.
If that doesn't work try : npm install --global npm
Your OS is different to the OS from which you got the code from.
Solution: deleting the file .browserslistrc should work.
Related
i am following the tutorial https://helpx.adobe.com/experience-manager/kt/sites/using/getting-started-spa-wknd-tutorial-develop/react/chapter-0.html#integrate-react-app for integrating reactjs with AEM,i am facing issue while running "mvn clean install" and i was able to perform previous steps properly.
C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app>mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO] ---------< com.adobe.aem.guides:aem-guides-wknd-events.react >----------
[INFO] Building WKND Events - React App 0.0.1-SNAPSHOT
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) # aem-guides-wknd-events.react ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) # aem-guides-wknd-events.react ---
[INFO]
[INFO] --- frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) # aem-guides-wknd-events.react ---
[INFO] Installing node version v10.8.0
[INFO] Copying node binary from C:\Users\TEJA\.m2\repository\com\github\eirslett\node\10.8.0\node-10.8.0-win-x64.exe to C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app\node\node.exe
[INFO] Installed node locally.
[INFO] NPM 6.2.0 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install) # aem-guides-wknd-events.react ---
[INFO] Running 'npm install' in C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.810 s
[INFO] Finished at: 2019-10-20T23:44:11+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:npm (npm install) on project aem-guides-wknd-events.react: Failed to run task: 'npm install' failed. java.io.IOException: Cannot run program "C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app\node\node.exe" (in directory "C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app"): CreateProcess error=193, %1 is not a valid Win32 application -> [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/MojoFailureException
C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app>npm install aem-clientlib-generator --save-dev
npm WARN ajv-keywords#3.2.0 requires a peer of ajv#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ aem-clientlib-generator#1.4.4
updated 1 package and audited 33138 packages in 31.111s
found 1041 vulnerabilities (71 low, 8 moderate, 960 high, 2 critical)
run `npm audit fix` to fix them, or `npm audit` for details
C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app>mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO] ---------< com.adobe.aem.guides:aem-guides-wknd-events.react >----------
[INFO] Building WKND Events - React App 0.0.1-SNAPSHOT
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) # aem-guides-wknd-events.react ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) # aem-guides-wknd-events.react ---
[INFO]
[INFO] --- frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) # aem-guides-wknd-events.react ---
[INFO] Installing node version v10.8.0
[INFO] Copying node binary from C:\Users\TEJA\.m2\repository\com\github\eirslett\node\10.8.0\node-10.8.0-win-x64.exe to C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app\node\node.exe
[INFO] Installed node locally.
[INFO] NPM 6.2.0 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install) # aem-guides-wknd-events.react ---
[INFO] Running 'npm install' in C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.590 s
[INFO] Finished at: 2019-10-20T23:45:29+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:npm (npm install) on project aem-guides-wknd-events.react: Failed to run task: 'npm install' failed. java.io.IOException: Cannot run program "C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app\node\node.exe" (in directory "C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app"): CreateProcess error=193, %1 is not a valid Win32 application -> [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/MojoFailureException
C:\Users\TEJA\Desktop\Start-aem-wknd-events-react\Start\aem-guides-wknd-events\react-app>mvn clean install
I have used frontend-maven-plugin without issues in other projects, by reading the error message, it seems it is common that the npm.exe executable gets corrupted.
Try deleting your .m2 plugin directory or specifying a custom npm version <npmVersions>.
See issue 487 on GitHub
The issue might be in the script in one of the react/webpack config files. Search for "%1" in the directory, %1 may be passed as a parameter in the script/command
%1 is not a valid Win32 application
Usually these are linux commands and will fail to work in windows machines. Can you try installing this in a linux machine?
I am officially porting OrientDB (community release) on powerpc ( ppc64le ) . I have cloned the repo from here and followed build steps as below :
$ git clone https://github.com/orientechnologies/orientdb
$ git checkout develop
$ cd orientdb
$ mvn clean install
However getting test case failures as below
Failed tests:
TestBatchRemoteResultSet.runBatchQuery:59
Tests in error:
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexBatch:87 » ODatabase Datab...
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexFromSubquery:114 » ODatabase
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexFromSubquery2:127 » ODatabase
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexLimit:72 » ODatabase Datab...
SimplePropertyLinkTest.testSimplePropertyLink:27 ClassCast java.lang.String in...
Tests run: 384, Failures: 1, Errors: 5, Skipped: 123
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] OrientDB ........................................... SUCCESS [ 3.305 s]
[INFO] OrientDB Test Commons .............................. SUCCESS [ 5.100 s]
[INFO] OrientDB Core ...................................... SUCCESS [03:11 min]
[INFO] OrientDB Client .................................... SUCCESS [ 7.290 s]
[INFO] OrientDB Object .................................... SUCCESS [ 15.109 s]
[INFO] OrientDB Tools ..................................... SUCCESS [ 9.159 s]
[INFO] OrientDB Server .................................... SUCCESS [ 39.269 s]
[INFO] OrientDB GraphDB ................................... FAILURE [01:11 min]
[INFO] OrientDB Tests ..................................... SKIPPED
[INFO] OrientDB Distributed Server ........................ SKIPPED
[INFO] OrientDB Lucene full text index .................... SKIPPED
[INFO] OrientDB JDBC Driver ............................... SKIPPED
[INFO] OrientDB ETL ....................................... SKIPPED
[INFO] OrientDB Community Distribution .................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:43 min
[INFO] Finished at: 2016-06-15T13:25:21+05:30
[INFO] Final Memory: 134M/227M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project orientdb-graphdb: There are test failures.
[ERROR]
[ERROR] Please refer to /root/amit/rethinkDB/orientDB_dev/graphdb/target/surefire-reports for the individual test results.
[ERROR] -> [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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :orientdb-graphdb
[1]: https://github.com/orientechnologies/orientdb
Any pointers on this , have raised a git issue ticket here , but thought of asking here if anyone has seen such errors.
I do not have this SFTP jar in my Nexus Repo & I have add it's dependency into the POM file but now i want to install this JAR in my local repository so that i can use it in my project. But getting access is denied even though i opened command prompt with Administrator rights.
C:\Windows\system32>mvn install:install-file -DgroupId=org.springframework.integration -DartifactId=spring-integration-sftp -Dversion=4.1.5 -Dpackaging=jar -Dfile=C:\Repo
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-install-plugin:2.4:install-file (default-cli) # standalone-pom
---
[INFO] Installing C:\Repo to C:\Users\t868396\.m2\repository\org\springframework
\integration\spring-integration-sftp\4.1.5\spring-integration-sftp-4.1.5.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.827 s
[INFO] Finished at: 2015-06-23T11:02:52+05:00
[INFO] Final Memory: 15M/64M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4
:install-file (default-cli) on project standalone-pom: Error installing artifact
'org.springframework.integration:spring-integration-sftp:jar': Failed to instal
l artifact org.springframework.integration:spring-integration-sftp:jar:4.1.5: C:
\Repo (Access is denied) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
Mostly likely the -Dfile=your.jar is not correct, check your argument (FYI it was omitted from your posting).
Here is an example:
mvn install:install-file -DlocalRepositoryPath=repo -DcreateChecksum=true
-Dfile=[your-jar] -Dpackaging=jar
-DgroupId=[...] -DartifactId=[...] -Dversion=[...]
See: Can I add jars to maven 2 build classpath without installing them?
And: https://maven.apache.org/general.html#importing-jars
I'm trying to use the cargo plugin to run a web application in a local Jetty container from inside Eclipse. This seems to be working for other people with the exact same pom.xml, but I get this error:
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.0.3:start (default-cli) on project wsc: Failed to resolve dependency: C:\Program Files\Java\lib\tools.jar -> [Help 1]
How do I resolve this? The project is set to use jdk1.7.0 as the "JRE System Library". I am starting Eclipse with "-vm " and even JAVA_HOME is set to the JDK path.
Any ideas? I've been researching on this for a while and getting crazy about that. The documentation on including tools.jar as dependency didn't help me.
Important: This seems to work outside Eclipse, e.g. with mvn -P local cargo:start.
Program output when started from Eclipse:
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Web Services Computing 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- cargo-maven2-plugin:1.0.3:start (default-cli) # wsc ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.324s
[INFO] Finished at: Sat Oct 22 19:10:18 CEST 2011
[INFO] Final Memory: 15M/107M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.0.3:start (default-cli) on project wsc: Failed to resolve dependency: C:\Program Files\Java\lib\tools.jar -> [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
Dependency tree output (also started from Eclipse):
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) # wsc ---
[INFO] de.tum.ibis.wsc:wsc:war:0.0.1-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] \- javax.servlet:servlet-api:jar:2.5:compile
[INFO] ------------------------------------------------------------------------
You have to start eclipse with a jdk instead of a jre.
If you edit your eclipse.ini and put a jdk to the vm arguments it should work.
-vm
C:/java_1_6/jdk/bin/javaw.exe
I'm trying to create the meta-data for a eclipse project in maven, but my parter and I keep running into the following error, on both our machines. Ive looked around the forum and have tried related advice such as defining a path in the eclipse.ini file and so on, but this hasn't worked. Has anyone else ran into this error before or can see what I am doing incorrectly? Any help would be greatly appreciated.
C:\Users\jheerman\workspace\release\admin-portal>mvn eclipse:clean eclipse:eclip
se -DdownloadSources=true
[INFO] Scanning for projects...
[WARNING] The POM for org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1 is missi
ng, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.codeaus.mojo:rpm-maven-pl
ugin:2.1-alpha-1: Plugin org.codeaus.mojo:rpm-maven-plugin:2.1-alpha-1 or one of
its dependencies could not be resolved: Failed to read artifact descriptor for
org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1
[WARNING] The POM for org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1 is missi
ng, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.codeaus.mojo:rpm-maven-pl
ugin:2.1-alpha-1: Plugin org.codeaus.mojo:rpm-maven-plugin:2.1-alpha-1 or one of
its dependencies could not be resolved: Failed to read artifact descriptor for
org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building CTP Admin Portal Services 0.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1 is missi
ng, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.codeaus.mojo:rpm-maven-pl
ugin:2.1-alpha-1: Plugin org.codeaus.mojo:rpm-maven-plugin:2.1-alpha-1 or one of
its dependencies could not be resolved: Failed to read artifact descriptor for
org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1
[WARNING] The POM for org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1 is missi
ng, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.codeaus.mojo:rpm-maven-pl
ugin:2.1-alpha-1: Plugin org.codeaus.mojo:rpm-maven-plugin:2.1-alpha-1 or one of
its dependencies could not be resolved: Failed to read artifact descriptor for
org.codeaus.mojo:rpm-maven-plugin:jar:2.1-alpha-1
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:clean (default-cli) # ctp-admin-portal ---
[INFO] Deleting file: .project
[INFO] Deleting file: .classpath
[INFO] Deleting file: .wtpmodules
[INFO] Deleting file: .component
[INFO] Deleting file: org.eclipse.wst.common.component
[INFO] Deleting file: org.eclipse.wst.common.project.facet.core.xml
[INFO] Deleting file: org.eclipse.jdt.core.prefs
[INFO] Deleting file: org.eclipse.ajdt.ui.prefs
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) # ctp-admin-portal >>>
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) # ctp-admin-portal <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) # ctp-admin-portal ---
[INFO] Using Eclipse Workspace: C:\Users\jheerman\workspace
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
ER
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 34.003s
[INFO] Finished at: Thu Jun 23 09:42:31 GMT-08:00 2011
[INFO] Final Memory: 8M/19M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.8
:eclipse (default-cli) on project ctp-admin-portal: Cant canonicalize system pat
h: {0}: The filename, directory name, or volume label syntax is incorrect -> [He
lp 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception