[ http://jira.codehaus.org/browse/MNG-382?page=all ]
     
Emmanuel Venisse closed MNG-382:
--------------------------------

    Resolution: Fixed

a basic version is done.

> implement basic release plugin
> ------------------------------
>
>          Key: MNG-382
>          URL: http://jira.codehaus.org/browse/MNG-382
>      Project: m2
>         Type: New Feature
>   Components: maven-plugins
>     Reporter: Brett Porter
>     Assignee: Emmanuel Venisse
>      Fix For: 2.0-alpha-3

>
>
> I think it should, to start off with, be similar to the functionality from 
> the SCM plugin (though we can use the more sensible "release" plugin name 
> now) in Maven 1.x. The SCM 1.5 beta plugin uses Maven-SCM, so should be 
> reusable.
> General reqs:
> - There are two stages: preparation of the release (which gets the "released" 
> code into the SCM), and perform the release (which does a clean checkout from 
> SCM and runs specified deployment goals).
> - In the event that the user is not using an SCM, I think we just reuse 
> what's in the current directory in both cases.
> - Work with modules, so you can share a version like all of m2 (except 
> plugins) does.
> For preparation:
> - check SCM preconditions (eg, test no uncommitted files in the WD)
> - check for any snapshot references in artifacts (dependencies, and 
> transitively resolved), plugins and parent. Based on configuration, fail or 
> resolve to timestamp. Will have to fail if it is in a transitive dep.
> - check for unpopulated version in plugin or parent (ie effectively RELEASE), 
> and populate with the right version to make it reproducible in future
> - update the <version/> tag with the specified release version (where it 
> should have previously been
> - commit modified poms, and tag with the release tag
> For perform:
> - change the current deployment stuff that is writing the RELEASE files to 
> only do that at release time
> - do a clean checkout, and perform a set of tasks on them (deploy, 
> site:deploy). Am ok for this to just be "deploy" at this point.
> optional:
> - possibly should have a lifecycle setup that allows other plugins to hook in 
> to perform some tasks on 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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to