[jira] Issue Comment Edited: (MRELEASE-352) Record Maven version and java version used during release.

["Baptiste MATHUS (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233317#action_233317 ] 

Baptiste MATHUS edited comment on MRELEASE-352 at 8/27/10 7:38 AM:
-------------------------------------------------------------------

This is a very good idea, but I'm not sure this must be done by the release plugin. This is really something that's always useful to know afterwards, even with snapshots, not only for releases. I think this should always be done for packaging. 

Moreover, some people or organization can't use the release plugin, so their packaging would not contain this particularly interesting informations.

Cheers

      was (Author: batmat):
    This is a good idea, but I'm not sure this must be done by the release plugin. This is really something that's always useful to know afterwards, even with snapshots. I think this should always be done for packaging.

Cheers
  
> Record Maven version and java version used during release.
> ----------------------------------------------------------
>
>                 Key: MRELEASE-352
>                 URL: http://jira.codehaus.org/browse/MRELEASE-352
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: perform
>            Reporter: Paul Gier
>
> The release plugin should be able to record the version of Maven and the version of the JDK that were used when the release was done.
> For example, the prepare phase could write a file called environment-settings.xml that contains the version of Maven and of Java that were used during the prepare step.  This file could look something like this:
> {code:xml} 
> <environment>
>   <maven>
>     <version>2.0.8</version>
>   </maven>
>   <java>
>     <version>1.4.2_15</version>
>     <vendor>sun</vendor>
>   </java>
>   <os>
>     <name>windows</name>
>     ...
>   </os>
> </environment>
> {code}
> The perform part of the release would then make sure that these settings match when the project is re-built and deployed.  There could also be another goal in the release plugin, like "check-environment" that would check that the environment settings match.  That goal could be used when trying to rebuild an old release.

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