The Open Anzo Project

Semantic Application Middleware

Ticket #13 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

maven build throws IllegalArgumentException during test phase for anzo-maven

Reported by: jpbetz Assigned to: ben
Priority: major Milestone:
Component: openanzo Version: SNAPSHOT
Keywords: maven build Cc: ben, mroy

Description (Last modified by jpbetz)

cd anzo-maven
maven package
...
java.lang.IllegalArgumentException
       at java.lang.ProcessImpl.<init>(ProcessImpl.java:69)
       at java.lang.ProcessImpl.start(ProcessImpl.java:30)
       at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
       at java.lang.Runtime.exec(Runtime.java:591)
...

Attachments

maven.log (2.8 kB) - added by jpbetz on 09/28/07 17:46:05.
maven log snippet

Change History

09/28/07 17:37:24 changed by jpbetz

  • cc changed from ben to ben, mroy.
  • owner changed from mroy to ben.

Found exact same stack trace on google:

http://www.mail-archive.com/users@maven.apache.org/msg71022.html

This mailing list entry claims the issue is caused by some combination of versions of TestNG and Surefire. Only we don't use TestNG, we use junit instead. In my repository I don't even have TestNG..

Ben, out of curiosity, would you look in your maven repo and see which version of surefire maven pulled down for you?

cd ~/.m2/repo ls org/apache/maven/surefire/surefire

would you also check to see if you have testNG in your repo, path should be something like:

org/testng/testng

?

09/28/07 17:44:50 changed by jpbetz

  • description changed.

09/28/07 17:46:05 changed by jpbetz

  • attachment maven.log added.

maven log snippet

09/28/07 17:47:44 changed by jpbetz

  • description changed.

09/28/07 22:44:05 changed by jpbetz

  • status changed from new to closed.
  • resolution set to fixed.

Cruise control is failing builds too:

http://www.openanzo.org:8180/cruisecontrol/buildresults/openanzo?log=log20070928215522

<pre> ... Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/surefire/surefire-testng/2.4-SNAPSHOT/surefire-testng-2.4-20070827.165719-8.jar ... </pre>

so it looks like surefire's latest snapshot is the culprit.

see also: http://jira.codehaus.org/browse/SUREFIRE-59

Fixed with r325 by locking surefire plugin to version 2.4-collab-SNAPSHOT.

10/02/07 20:12:33 changed by jpbetz

Anyone experiencing this after r325 should remove the org/apache/maven/surefire/surefire-testing directory from their local maven repository (~/.m2/repository by default) to force maven to update.

Copyright © 2007 - 2008 OpenAnzo.org