maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MINVOKER-106) invoker.java.version is always evaluated against current JVM instead of JVM running the builds
Date Mon, 12 Nov 2012 21:12:13 GMT

     [ 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

        

Mime
View raw message