[
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
