[
http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171660#action_171660
]
Brett Porter commented on MNG-4112:
-----------------------------------
that's exactly what the runtimeinformation does. I misunderstood what Jason
meant on the list by "making it work". If you're happy to settle for making a
change to Maven, then putting maven.version into the context for interpolation
and anything else that is going to grab it from the session is probably the
right way to go. I had the feeling 3.x already has this, but 2.1 doesn't -
would need to check though.
> Set property containing the currently executing maven version.
> --------------------------------------------------------------
>
> Key: MNG-4112
> URL: http://jira.codehaus.org/browse/MNG-4112
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Paul Gier
>
> It would be helpful to have an easy way to access the current version of
> maven. This might be accomplished by setting a property like "maven.version"
> during startup that would be available to the pom and/or to plugins. This
> could be used to record what version of maven was used during the build to
> facilitate build reproducibility.
--
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
