You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/08/07 13:53:32 UTC
[jira] Created: (MINVOKER-106) invoker.java.version is always
evaluated against current JVM instead of JVM running the builds
invoker.java.version is always evaluated against current JVM instead of JVM running the builds
----------------------------------------------------------------------------------------------
Key: MINVOKER-106
URL: http://jira.codehaus.org/browse/MINVOKER-106
Project: Maven 2.x Invoker Plugin
Issue Type: Bug
Affects Versions: 1.5
Reporter: Benjamin Bentmann
Priority: Minor
The selector condition for the JVM version always looks at the current JVM, not the JVM that will be used to run the forked builds. This gets only obvious when using invoker.javaHome to point at a different JVM than the one running the Invoker 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] (MINVOKER-106) invoker.java.version is always evaluated
against current JVM instead of JVM running the builds
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MINVOKER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reassigned MINVOKER-106:
---------------------------------------
Assignee: Robert Scholte
> invoker.java.version is always evaluated against current JVM instead of JVM running the builds
> ----------------------------------------------------------------------------------------------
>
> Key: MINVOKER-106
> URL: https://jira.codehaus.org/browse/MINVOKER-106
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Benjamin Bentmann
> Assignee: Robert Scholte
> Priority: Minor
>
> The selector condition for the JVM version always looks at the current JVM, not the JVM that will be used to run the forked builds. This gets only obvious when using invoker.javaHome to point at a different JVM than the one running the Invoker Plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-106) invoker.java.version is always evaluated
against current JVM instead of JVM running the builds
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MINVOKER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MINVOKER-106.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.8
Fixed in [r1408460|http://svn.apache.org/viewvc?rev=1408460&view=rev]
> invoker.java.version is always evaluated against current JVM instead of JVM running the builds
> ----------------------------------------------------------------------------------------------
>
> Key: MINVOKER-106
> URL: https://jira.codehaus.org/browse/MINVOKER-106
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Benjamin Bentmann
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 1.8
>
>
> The selector condition for the JVM version always looks at the current JVM, not the JVM that will be used to run the forked builds. This gets only obvious when using invoker.javaHome to point at a different JVM than the one running the Invoker Plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-106) invoker.java.version is always evaluated
against current JVM instead of JVM running the builds
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MINVOKER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312488#comment-312488 ]
Robert Scholte commented on MINVOKER-106:
-----------------------------------------
One way to figure it out is by calling {java.home}/bin/java -version and parse the output, but I'm not sure if this is vendor specific.
> invoker.java.version is always evaluated against current JVM instead of JVM running the builds
> ----------------------------------------------------------------------------------------------
>
> Key: MINVOKER-106
> URL: https://jira.codehaus.org/browse/MINVOKER-106
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Benjamin Bentmann
> Priority: Minor
>
> The selector condition for the JVM version always looks at the current JVM, not the JVM that will be used to run the forked builds. This gets only obvious when using invoker.javaHome to point at a different JVM than the one running the Invoker Plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira