maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRELEASE-352) Record Maven version and java version used during release.
Date Thu, 05 Jun 2008 16:23:54 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Gier updated MRELEASE-352:
-------------------------------

    Description: 
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.


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

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.



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

        

Mime
View raw message