You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/12/31 07:05:55 UTC
[jira] Updated: (MNG-4112) Set property containing the currently
executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4112:
------------------------------
Fix Version/s: (was: 2.3.x)
3.0-alpha-7
2.2.2
I remember this being bounced around on list - we need to define the canonical way to get the maven version and make sure it works in 2.2.x and 3.0
> Set property containing the currently executing maven version.
> --------------------------------------------------------------
>
> Key: MNG-4112
> URL: http://jira.codehaus.org/browse/MNG-4112
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Paul Gier
> Fix For: 2.2.2, 3.0-alpha-7
>
> Attachments: MNG-4112-maven-embedder.patch
>
>
> 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