You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Hoffer (JIRA)" <ji...@codehaus.org> on 2007/04/19 20:00:46 UTC
[jira] Created: (MRELEASE-216) Release plugin should ignore
SNAPSHOTS that are not specified in the POM
Release plugin should ignore SNAPSHOTS that are not specified in the POM
------------------------------------------------------------------------
Key: MRELEASE-216
URL: http://jira.codehaus.org/browse/MRELEASE-216
Project: Maven 2.x Release Plugin
Issue Type: Bug
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-216) Release plugin should ignore
SNAPSHOTS that are not specified in the POM
Posted by "Luca Dall'Olio (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93487 ]
Luca Dall'Olio commented on MRELEASE-216:
-----------------------------------------
Same thing when using continuum :-)
> Release plugin should ignore SNAPSHOTS that are not specified in the POM
> ------------------------------------------------------------------------
>
> Key: MRELEASE-216
> URL: http://jira.codehaus.org/browse/MRELEASE-216
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-216) Release plugin should ignore
SNAPSHOTS that are not specified in the POM
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-216:
-------------------------------------
Component/s: prepare
> Release plugin should ignore SNAPSHOTS that are not specified in the POM
> ------------------------------------------------------------------------
>
> Key: MRELEASE-216
> URL: http://jira.codehaus.org/browse/MRELEASE-216
> Project: Maven 2.x 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-216) Release plugin should ignore
SNAPSHOTS that are not specified in the POM
Posted by "Michael McCallum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240086#action_240086 ]
Michael McCallum commented on MRELEASE-216:
-------------------------------------------
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.
> Release plugin should ignore SNAPSHOTS that are not specified in the POM
> ------------------------------------------------------------------------
>
> Key: MRELEASE-216
> URL: http://jira.codehaus.org/browse/MRELEASE-216
> Project: Maven 2.x 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira