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

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MRELEASE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-216.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Release plugin should ignore SNAPSHOTS that are not specified in the POM
> ------------------------------------------------------------------------
>
>                 Key: MRELEASE-216
>                 URL: https://jira.codehaus.org/browse/MRELEASE-216
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-4
>         Environment: XP Pro SP2
>            Reporter: David Hoffer
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)