John,

I thought release-pom.xml was disabled due to numerous problems, which
is probably why this was gone.

Are all the issues regarding release-pom resolved? Until they are, using
the normal poms is better than something that has absolute paths or too
much info. Let's make sure the right stuff goes into the repo for 2.0.1.

- Brett

John Casey (JIRA) wrote:
>      [ http://jira.codehaus.org/browse/MNG-1713?page=all ]
>      
> John Casey closed MNG-1713:
> ---------------------------
> 
>     Resolution: Fixed
> 
> added an install step to the it2002 test.
> 
> NOTE: release of a multimodule project somehow still depends on a previous 
> install build of the project artifacts to the local repo. Will file another 
> issue to investigate this further.
> 
> Also, I had to add SCM handling for release-pom.xml files, so they are 
> checked in and removed properly. Not sure where this fell off the map...
> 
>> Option not to run install phase during realease:prepare
>> -------------------------------------------------------
>>
>>          Key: MNG-1713
>>          URL: http://jira.codehaus.org/browse/MNG-1713
>>      Project: Maven 2
>>         Type: Wish
>>   Components: maven-release-plugin
>>     Versions: 2.0
>>  Environment: xp,clearcase,starteam
>>     Reporter: Dan Tran
>>     Assignee: John Casey
>>      Fix For: 2.0.1
> 
>>
>> 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?
> 


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

Reply via email to