You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Smiley (JIRA)" <ji...@codehaus.org> on 2006/12/05 15:03:41 UTC

[jira] Commented: (MRELEASE-62) Option not to run install phase during realease:prepare

    [ http://jira.codehaus.org/browse/MRELEASE-62?page=comments#action_81811 ] 
            
David Smiley commented on MRELEASE-62:
--------------------------------------

As of this date, release:prepare appears not to run the install phase.  I looked in my local repo and I didn't find the version I just prepared.  I'd definitely prefer my releases to be installed because I might forget otherwise.

> Option not to run install phase during realease:prepare
> -------------------------------------------------------
>
>                 Key: MRELEASE-62
>                 URL: http://jira.codehaus.org/browse/MRELEASE-62
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>         Environment: xp,clearcase,starteam
>            Reporter: Dan Tran
>         Assigned To: John Casey
>
> I have a build environments where daily release build is required and the build is long ( 1 - 2 hours is the norm).
> By using the current release plugin, the prepare step forces the install phase, we end up to do the build at both
> prepare and perform steps and therefore the build time is double.
> I would like to propose that maven-release-plugin allows an option not to invoke the install phase. Here are my
> thoughts on this.
>    - Fail daily build is a norm, however failure is selfdom now with the help of contiguous integration (ie Continuum).
>      
>    - Since the build is long, passing the prepare phase, does not mean it will pass at perform phase since user
>      can checkin changes at the build phase in prepare step. 
> Thoughts?
> Would binding preprare mojo to initialize phase is good enought? how can we optionally change the execute phase
> at run time?

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