You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "geoff simpson (JIRA)" <ji...@codehaus.org> on 2007/03/01 14:27:43 UTC
[jira] Created: (SUREFIRE-299) jvm flag broken
jvm flag broken
---------------
Key: SUREFIRE-299
URL: http://jira.codehaus.org/browse/SUREFIRE-299
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.0 (2.2 plugin)
Environment: winXP
Reporter: geoff simpson
it appears the jvm flag is not working, trying to run maven using jdk1.4 and fork the compiler for one of the projects to jdk1.5 the code compiles ok but the test is still run as jdk 1.4 when forkMode is set to pertest. this works ok in version 2.1 of the plugin.
--
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-299) jvm flag broken
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-299.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.4)
This must have gotten fixed at some point. It's working for me with the "fork-mode" integration test checked into the 2.4 trunk.
> jvm flag broken
> ---------------
>
> Key: SUREFIRE-299
> URL: http://jira.codehaus.org/browse/SUREFIRE-299
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Environment: winXP
> Reporter: geoff simpson
>
> it appears the jvm flag is not working, trying to run maven using jdk1.4 and fork the compiler for one of the projects to jdk1.5 the code compiles ok but the test is still run as jdk 1.4 when forkMode is set to pertest. this works ok in version 2.1 of the plugin.
--
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-299) jvm flag broken
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-299:
----------------------------------
Fix Version/s: 2.4
> jvm flag broken
> ---------------
>
> Key: SUREFIRE-299
> URL: http://jira.codehaus.org/browse/SUREFIRE-299
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Environment: winXP
> Reporter: geoff simpson
> Fix For: 2.4
>
>
> it appears the jvm flag is not working, trying to run maven using jdk1.4 and fork the compiler for one of the projects to jdk1.5 the code compiles ok but the test is still run as jdk 1.4 when forkMode is set to pertest. this works ok in version 2.1 of the plugin.
--
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