You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2013/10/24 09:10:52 UTC

[jira] (MINVOKER-122) Import information into groovy scripts of the running Maven environment

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

Anders Hammar commented on MINVOKER-122:
----------------------------------------

I'd also like to see info on the Maven version being injected as a variable. Maven 3.0.4+ makes this info available as a property, but not sure how we can handle other Maven versions.
                
> Import information into groovy scripts of the running Maven environment 
> ------------------------------------------------------------------------
>
>                 Key: MINVOKER-122
>                 URL: https://jira.codehaus.org/browse/MINVOKER-122
>             Project: Maven Invoker Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.5
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> During the execution of a postbuild.groovy script i'm checking the contents of the build.log output (output of plugins etc.). The problem is that based on the differences between MVN 2.2.1 and MVN 3.0.? the output looks different. But inside a verify.groovy i don't know under which version of Maven the integration-tests has been run...so it's not simple to make a difference here...It might be a good idea to get this information inside the groovy script.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira