Option not to run install phase during realease:prepare

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    xp,clearcase,starteam

Description

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?

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-3 release:prepare should not require multimodule artifacts to be in the local repository

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

I don't think install should be run at all. It was introduced in rev 329946 by John, for issue: http://jira.codehaus.org/browse/MNG-1101. But nothing in that issue or the log comment indicate the reason. John?

Show
Brett Porter added a comment - I don't think install should be run at all. It was introduced in rev 329946 by John, for issue: http://jira.codehaus.org/browse/MNG-1101. But nothing in that issue or the log comment indicate the reason. John?
Hide
Permalink
John Casey added a comment -

it seems to me this had to do with resolving dependencies in the release process that were part of the multimodule build being released.

I'll try to back the change back out, and see if I can get it to work.

Show
John Casey added a comment - it seems to me this had to do with resolving dependencies in the release process that were part of the multimodule build being released. I'll try to back the change back out, and see if I can get it to work.
Hide
Permalink
John Casey added a comment -

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

Show
John Casey added a comment - 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...
Hide
Permalink
David Smiley added a comment -

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.

Show
David Smiley added a comment - 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.

People

  • Assignee:
    John Casey
    Reporter:
    Dan Tran
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: