Lol don't consider that, that was a lame attempt to obfuscate few
internal details as asked by my company...
See my next answer for more details with normal logs, sorry about that.
Alexis.
Le 27/04/2012 17:37, Wayne Fay a écrit :
Please refer to
D:\Jenkins-slave\workspace\<jobname>\<modulename>\target\surefire-reports
for the individual test results.
Does the log literally say<jobname> and<modulename>? If so, this
suggests an error in how Jenkins is calling your Maven build (to me at
least).
[JENKINS] Archiving
D:\Jenkins-slave\workspace\<jobname>\<modulename>\pom.xml to
/opt/jenkins/projects/jobs/<jobname>/modules/<gpId>$<artId>/builds/2012-04-27_16-16-40/archive/<gpId>/<artId>/2.1.020.000-SNAPSHOT/cms-xmlengine-2.1.020.000-SNAPSHOT.pom
Here we see<gpId> and $<artId> which seem wrong.
Caused by: org.apache.maven.plugin.PluginManagerException: Failed to read
D:\Jenkins-slave\workspace\OT_1.2-OAMP-CMS-Deploy_All_Inc15mn\xmlengine\cms-xmlengine\target\surefire-reports\result.xml
Here in the log it looks like the groupIds and artifactIds are fully resolved.
There is a lot going on here. I don't know where to begin.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
