[
https://jira.codehaus.org/browse/MRELEASE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-352.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
With MSHARED-38 both the JDK and Maven version can included in the MANIFEST
file.
This way the information is available to rerun the build with the same
environment.
> 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
> Assignee: Robert Scholte
>
> 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
