You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Denis Cabasson (JIRA)" <ji...@codehaus.org> on 2007/04/02 16:16:06 UTC
[jira] Created: (MNG-2920) [M206] Test doesn't work anymore
[M206] Test doesn't work anymore
--------------------------------
Key: MNG-2920
URL: http://jira.codehaus.org/browse/MNG-2920
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.6
Environment: Windows XP
Reporter: Denis Cabasson
Priority: Blocker
Attachments: 206-test.zip, test-exec-205.txt, test-exec-206.txt
When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Gamnacke (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98247 ]
Gamnacke commented on SUREFIRE-316:
-----------------------------------
I can confirm this too. I use Maven 2.0.6 and tried both maven-surefire-plugin 2.3 as well as 2.4-SNAPSHOT. None of them work for me.
I get the following exception:
[INFO] [surefire:test]
[INFO] Surefire report directory: C:\workspaces\wcar-om\wcar-om-ejb\target\surefire-reports
[INFO] Building jar: C:\DOCUME~1\jon\LOCALS~1\Temp\surefirebooter16105.jar
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
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:452)
at java.lang.Runtime.exec(Runtime.java:593)
at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:653)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:102)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89)
at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:576)
at org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:413)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:313)
at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:203)
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:397)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Mon Jun 04 09:06:44 CEST 2007
[INFO] Final Memory: 5M/9M
[INFO] ------------------------------------------------------------------------
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated SUREFIRE-316:
------------------------------------
Priority: Major (was: Blocker)
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Jason Chaffee (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91815 ]
Jason Chaffee commented on SUREFIRE-316:
----------------------------------------
Ok, I will create a new issue. I have stated on several occasions that I am using version 2.3 of the surefire plugin with both 2.0.5 and 2.0.6 . It works in 2.0.5 and it does not work in 2.0.6. I actually do think these bugs are related because it is related to the forking and my case is causing a different Exception.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98249 ]
Brett Porter commented on SUREFIRE-316:
---------------------------------------
does it fail with the supplied test case? Or do you have an alternate test case that exhibits this?
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91818 ]
Carlos Sanchez commented on SUREFIRE-316:
-----------------------------------------
but the example you are putting doesn't have <version> tag, how are you setting the version of the plugin?
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2920) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MNG-2920:
--------------------------------
Attachment: diff.txt
here is the diff between 2.0.5 output and 2.0.6
The command line is definitely different
-Forking command line: "D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16110tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16111tmp
+Forking command line: cmd.exe /X /C '"D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15149tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15150tmp'
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: MNG-2920
> URL: http://jira.codehaus.org/browse/MNG-2920
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.6
> Environment: Windows XP
> Reporter: Denis Cabasson
> Priority: Blocker
> Attachments: 206-test.zip, diff.txt, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2920) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MNG-2920:
--------------------------------
Attachment: pom.xml
The problem only happens with surefire 2.3.1-SNAPSHOT
I've tried 2.3 and 2.4-SNAPSHOT and everything is fine
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: MNG-2920
> URL: http://jira.codehaus.org/browse/MNG-2920
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.6
> Environment: Windows XP
> Reporter: Denis Cabasson
> Priority: Blocker
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Gamnacke (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98252 ]
Gamnacke commented on SUREFIRE-316:
-----------------------------------
Sorry, my mistake surefire 2.3 does not fail, however, 2.4-SNAPSHOT does. I've created a minimal project that recreates the problem. I'll attach it in a few minutes.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Denis Cabasson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98273 ]
Denis Cabasson commented on SUREFIRE-316:
-----------------------------------------
Indeed, latest surefire version (surefire-2.4-20070602.002546-13) is broken in this respect.
Version 2.4-collab-SNAPSHOT is working fine, though. Where is this "collab" version comming from?
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105821 ]
Brett Porter commented on SUREFIRE-316:
---------------------------------------
surefire-collaboration is not active, the only active branches are trunk and -2.3.x. I'll take a look.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Jason Chaffee (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91827 ]
Jason Chaffee commented on SUREFIRE-316:
----------------------------------------
The version is being set in a parent pom that has the <pluginManagement>. The configuration I provided is the the specific configuration for a particular project that manifests this bug. In other words, I have the following config in the parent pom.xml:
<build>
<pluginManagement>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.3</version>
<configuration>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<trimStackTrace>false</trimStackTrace>
<systemProperties>
<property>
<name>user.dir</name>
<value>${basedir}</value>
</property>
<property>
<name>sun.net.client.defaultConnectTimeout</name>
<value>60000</value>
</property>
<property>
<name>sun.net.client.defaultReadTimeout</name>
<value>60000</value>
</property>
</systemProperties>
</configuration>
</plugin>
<pluginManagment>
</build>
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez moved MNG-2920 to SUREFIRE-316:
----------------------------------------------
Affects Version/s: (was: 2.0.6)
Key: SUREFIRE-316 (was: MNG-2920)
Project: Maven Surefire (was: Maven 2)
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Priority: Blocker
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Gamnacke (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gamnacke updated SUREFIRE-316:
------------------------------
Attachment: test.zip
Here is a minimal maven project that recreates the problem. I use maven 2.0.6. Build with "mvn package".
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Jason Chaffee (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91810 ]
Jason Chaffee commented on SUREFIRE-316:
----------------------------------------
> > This works fine in maven-2.0.5.
> >
> > I have the following surefire configuration:
> >
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-surefire-plugin</artifactId>
> > <configuration>
> > <forkMode>once</forkMode>
> >
> >
> <argLine>-javaagent:${project.build.directory}/test-lib/aspectjweaver.
> ja
> > r -Xmx256m</argLine>
> > </configuration>
> > </plugin>
> >
> > I get this error in 2.0.6
> >
> > [INFO] [surefire:test]
> > [INFO]
> >
> ----------------------------------------------------------------------
> --
> > [ERROR] FATAL ERROR
> > [INFO]
> >
> ----------------------------------------------------------------------
> --
> > [INFO] null
> > [INFO]
> >
> ----------------------------------------------------------------------
> --
> > [INFO] Trace
> > java.lang.NullPointerException
> > at
> > org.apache.maven.artifact.DefaultArtifact.getSelectedVersion(Default
> > A
> > rtifact.java:582)
> > at
> > org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBoo
> > t
> > er(SurefirePlugin.java:490)
> > at
> > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlug
> > i
> > n.java:391)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlug
> > i
> > nManager.java:443)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
> > a
> > ultLifecycleExecutor.java:539)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
> > i
> > fecycle(DefaultLifecycleExecutor.java:480)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defa
> > u
> > ltLifecycleExecutor.java:459)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
> > n
> > dleFailures(DefaultLifecycleExecutor.java:311)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
> > n
> > ts(DefaultLifecycleExecutor.java:278)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultL
> > i
> > fecycleExecutor.java:143)
> > at
> > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> > at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
> > s
> > sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at
> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430
> > )
> >
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Marat Radchenko (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marat Radchenko updated SUREFIRE-316:
-------------------------------------
Attachment: SUREFIRE-156.patch
Attached patch allows Surefire to pass testcase written by Gamnacke.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, SUREFIRE-156.patch, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SUREFIRE-316) [M206] Test doesn't
work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91801 ]
Carlos Sanchez edited comment on SUREFIRE-316 at 11/13/07 1:25 PM:
-------------------------------------------------------------------
here is the diff between 2.0.5 output and 2.0.6
The command line is definitely different
-Forking command line: "D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar; d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar; d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar; d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar; d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar; d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar; d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar; d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16110tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16111tmp
+Forking command line: cmd.exe /X /C '"D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar; d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar; d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar; d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar; d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar; d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar; d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar; d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15149tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15150tmp'
was:
here is the diff between 2.0.5 output and 2.0.6
The command line is definitely different
-Forking command line: "D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16110tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16111tmp
+Forking command line: cmd.exe /X /C '"D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15149tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15150tmp'
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, SUREFIRE-156.patch, SUREFIRE-316.patch, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105794 ]
Carlos Sanchez commented on SUREFIRE-316:
-----------------------------------------
Fixed by upgrading plexus-utils to 1.4.5 but now getting
java.lang.IllegalArgumentException: Unknown parameter type: java.util.Properties
at org.apache.maven.surefire.booter.SurefireBooter.constructParamObjects(SurefireBooter.java:800)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:855)
In rev 541168 the current lines 622-624 in SurefirePlugin.java were added but the required matching part in SurefireBooter.constructParamObjects was not added (it is in https://svn.apache.org/repos/asf/maven/sandbox/branches/surefire/surefire-collaboration/surefire-booter/src/main/java/org/apache/maven/surefire/booter/SurefireBooter.java)
Leaving to Brett that knows what's the status on the branches
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96443 ]
Barrie Treloar commented on SUREFIRE-316:
-----------------------------------------
Yes, probably PLXUTILS-31
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated SUREFIRE-316:
------------------------------------
Attachment: test.tgz
Jason, i can't reproduce your error, try attached sample
I imagine you just pasted the wrong xml, because you are missing the plugins tag between plugin and pluginManagement
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed SUREFIRE-316.
---------------------------------
Assignee: Brett Porter
Resolution: Cannot Reproduce
I believe this was fixed by reverting the plexus-utils to 1.1.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened SUREFIRE-316:
-----------------------------------
reopened for testing
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed SUREFIRE-316.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3.1)
2.4
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.4
>
> Attachments: 206-test.zip, diff.txt, pom.xml, SUREFIRE-156.patch, SUREFIRE-316.patch, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91811 ]
Carlos Sanchez commented on SUREFIRE-316:
-----------------------------------------
I don't see how that last comment relates to this issue, this one is about a IllegalArgumentException
Also try setting explicitly the plugin version as in attached pom to know what version of surefire plugin are you using
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-316:
----------------------------------
Fix Version/s: 2.3.1
this also seems to be plexus-utils related
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, test-exec-206.txt, test.tgz
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
Posted by "Marat Radchenko (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marat Radchenko updated SUREFIRE-316:
-------------------------------------
Attachment: SUREFIRE-316.patch
Woops, sorry, wrong patch. This one is correct.
> [M206] Test doesn't work anymore
> --------------------------------
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Denis Cabasson
> Assignee: Brett Porter
> Fix For: 2.3.1
>
> Attachments: 206-test.zip, diff.txt, pom.xml, SUREFIRE-156.patch, SUREFIRE-316.patch, test-exec-205.txt, test-exec-206.txt, test.tgz, test.zip
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira