You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/10/28 13:28:13 UTC

[jira] (MINVOKER-126) mavenHome in relationship with invoker.maven.version rule

    [ https://jira.codehaus.org/browse/MINVOKER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312486#comment-312486 ] 

Robert Scholte commented on MINVOKER-126:
-----------------------------------------

Added the ability to get the version based on the MavenHome in [r1402983|http://svn.apache.org/viewvc?rev=1402983&view=rev].
I've seen it working on my Win7 machine with M2.2.1 and M3.0.1, so this looks promising.
Next step requires some refactoring of the original code, since it calculates this value for every buildjob, which is way too expensive in my opinion.
                
> mavenHome in relationship with invoker.maven.version rule
> ---------------------------------------------------------
>
>                 Key: MINVOKER-126
>                 URL: https://jira.codehaus.org/browse/MINVOKER-126
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.5
>            Reporter: Karl Heinz Marbaise
>
> I've set up mavenHome in my POM to use Maven 2.2.1 but i have set a rule (invoker.maven.version = 2.2.0+, !3.0.0+) but the integration test is skipped anyway. 
> An assumtion of Rober Scholte was that invoker.maven.version works only for the executing Maven version which looks like. This results in two choices: either this is a bug or it should be clearly documented for the invoker.maven.version

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