[MRELEASE-216] Release plugin should ignore SNAPSHOTS that are not specified in the POM

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0-beta-4
• Component/s: prepare
• Environment: XP Pro SP2
• Assignee: Unassigned
• Reporter: David Hoffer
• Created: 19/Apr/07 12:59
• Updated: 25/Nov/14 14:48
• Resolved: 25/Nov/14 14:48

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: MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
• relates to: MENFORCER-94 Review evaluation of version ranges with regard to inclusion of snapshots