[
http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174620#action_174620
]
Petr Kozelka commented on MRELEASE-317:
---------------------------------------
In the meantime I started to use much better approach - the whole release runs
from within a specialized launcher that makes it use dedicated empty local
repository and settings.xml etc.
This is far much safer, because the release-specific settings.xml file mirrors
all requests to a nexus group that only has access to release repositories =>
it may never happen that a SNAPSHOT gets anywhere into release.
It also allows me to place other restrictions so that the release
reproducibility is as high as possible.
Now the release is slower (not important), but very very safe.
> release:prepare should fail if any pom depends on SNAPSHOT parent
> -----------------------------------------------------------------
>
> Key: MRELEASE-317
> URL: http://jira.codehaus.org/browse/MRELEASE-317
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: maven-2.0.8
> java-1.6
> Reporter: Petr Kozelka
> Priority: Critical
> Attachments: MRELEASE-317.patch.txt
>
>
> Currently the release plugin happily releases a pom that declares a SNAPSHOT
> version of parent.
> Such a release is exposed to a danger of irreproducibility:
> 1.) on another machine
> 2.) at another time (parent may significantly change in the meantime)
> While it can be sometimes convenient, it is, as I am quite sure, a bad
> behavior.
--
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
