Maven 2.x Release Plugin

Release plugin should ignore SNAPSHOTS that are not specified in the POM

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-4
  • Fix Version/s: None
  • Component/s: prepare
  • Labels:
    None
  • Environment:
    XP Pro SP2
  • Number of attachments :
    0

Description

The release plug-in has a major bug in the way it deals with SNAPSHOTS that are not specified in the artifact POM. It can fail for two reasons:

1. If the dependencies use set notation with an unbounded high end version, i.e. [1.0,) the release plug-in considers SNAPSHOTS when it looks for these dependencies. This makes it impossible to release anything if any dependency has been built on the same system with a higher SNAPSHOT version. Rather, it should ignore SNAPSHOTS as that was not the intent of the set notation version.
2. If building with TeamCity, the release will fail because TeamCity will generate a SNAPSHOT build of the current artifact between the release:prepare and release:perform tasks if VCS build triggering is turned on. This is because maven makes VCS commits during this process which TeamCity is triggered by.

These bugs make the release plug-in dependent on the content of the local repo instead of the POM. Also it makes it unusable with TeamCity.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3092 Version ranges with non-snapshot bounds can contain snapshot versions

  • Major - Major loss of function.
  • Reopened - This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
relates to

Task - A task that needs to be done. MENFORCER-94 Review evaluation of version ranges with regard to inclusion of snapshots

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Luca Dall'Olio added a comment -

Same thing when using continuum

Show
Luca Dall'Olio added a comment - Same thing when using continuum
Hide
Permalink
Michael McCallum added a comment -

Reconfigure your systems to not mix Ci and releasing. Don't ruin a perfectly good agile system for no reason.

I always release from a clean local repo you can easily configure a separate repo for releases and CI builds, from the output of mvn --help

s,-settings <arg> Alternate path for the user
settings file

So define a new settings file with a different <localRepository>xxx</localRepository> for doing the VCS builds... voila problem solved.
Having never used TeamCity there could be a bit more to it but i've used it with hudson quite successfully.

And use the enforcer plugin during release to double check that you have not got snapshots in there... Ranges are a bit useless for development if you don't include snapshots... And even the matching on boundaries like people have suggested... well you will still need to use the enforcer plugin so whats the point in changing the fundamental resolution? Its a process problem NOT a technical one.

Show
Michael McCallum added a comment - Reconfigure your systems to not mix Ci and releasing. Don't ruin a perfectly good agile system for no reason. I always release from a clean local repo you can easily configure a separate repo for releases and CI builds, from the output of mvn --help s, -settings <arg> Alternate path for the user settings file So define a new settings file with a different <localRepository>xxx</localRepository> for doing the VCS builds... voila problem solved. Having never used TeamCity there could be a bit more to it but i've used it with hudson quite successfully. And use the enforcer plugin during release to double check that you have not got snapshots in there... Ranges are a bit useless for development if you don't include snapshots... And even the matching on boundaries like people have suggested... well you will still need to use the enforcer plugin so whats the point in changing the fundamental resolution? Its a process problem NOT a technical one.

People

  • Assignee:
    Unassigned
    Reporter:
    David Hoffer
Vote (5)
Watch (6)

Dates

  • Created:
    Updated: