[jira] Updated: (SUREFIRE-204) [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.2-SNAPSHOT

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/SUREFIRE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated SUREFIRE-204:
----------------------------------

    Affects Version/s: 2.0 (2.2 plugin)

> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.2-SNAPSHOT 
> --------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-204
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-204
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>         Environment: Win XP, Sun jdk 1.5.0_06
>            Reporter: David J. M. Karlsen
>
> Launching a surefire test with a 1.3 JDK will fail as surefire sets -ea as a default option:
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.2-SNAPSHOT:test' -->
> .....
> Forking command line: C:\jdk1.3.1_18\bin\java.exe -ea -classpath < lots of classes >
> Unrecognized option: -ea
> The -ea option is not available on a 1.3.1 JDK - effectively disabling testing with a JDK < 1.4 with surefire.
> also tried setting an empty 
> <argLine/> in the configuration - but this didn't seem to be read (at least it's not mentioned while running with -X)
> Probably the options should all be set within <argLine> - and surefire should not assume any default options.

-- 
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