You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Noel Keating (JIRA)" <ji...@codehaus.org> on 2009/04/06 21:55:12 UTC

[jira] Commented: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent

    [ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172207#action_172207 ] 

Noel Keating commented on MRELEASE-317:
---------------------------------------

It seems that the CheckDependencySnapshotsPhase includes the parent artifact as part of it check, but the RewritePomPhases (AbstractRewritePomsPhase.rewriteParent) does not consider the resolvedSnapshotDependencies when transforming the pom file.

So even though you are asked to set the parent to released, a SNAPSHOT parent is committed.

> 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
>
> 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