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/06/02 16:12:21 UTC

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

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

Robert Scholte commented on MRELEASE-352:
-----------------------------------------

Is it a problem if the {{release:perform}} is executed with a different Maven version, Java version or OS then {{release:prepare}}? I think it is much more important to know with which environment the final/release version was built. Recently we've been able to add the Maven-version to the Manifest file.
I'd prefer to store this kind of information in that file, so that you should be able rebuild a project somewhere in the future with the same settings.
                
> Record Maven version and java version used during release.
> ----------------------------------------------------------
>
>                 Key: MRELEASE-352
>                 URL: https://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, 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