You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@codehaus.org> on 2007/08/21 10:24:47 UTC
[jira] Created: (MRELEASE-277) Unique versioned snapshots allowance
not covering always parent
Unique versioned snapshots allowance not covering always parent
---------------------------------------------------------------
Key: MRELEASE-277
URL: http://jira.codehaus.org/browse/MRELEASE-277
Project: Maven 2.x Release Plugin
Issue Type: Sub-task
Reporter: Tuomas Kiviaho
Attachments: CheckDependencySnapshotsPhaseTest.testAllowTimestampedParent.patch
Parent version could also be referenced by unique version number (assuming allowance to be set).
Problems arise when such parent is resolved to a file containing -SNAPSHOT marker instead of unique version number. See <http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-7-SNAPSHOT/maven-release-plugin-2.0-beta-7-20070531.213659-1.pom>
Reason is that whilst original model parent has the unique version artifact version is used instead.
There are uniquely versioned artifacts as well which (I assume) avoid the problem
See <http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-7-SNAPSHOT/maven-release-plugin-2.0-beta-7-20070726.151817-2.pom>
--
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-277) Unique versioned snapshots allowance
not covering always parent
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-277:
-------------------------------------
Component/s: prepare
> Unique versioned snapshots allowance not covering always parent
> ---------------------------------------------------------------
>
> Key: MRELEASE-277
> URL: http://jira.codehaus.org/browse/MRELEASE-277
> Project: Maven 2.x Release Plugin
> Issue Type: Sub-task
> Components: prepare
> Reporter: Tuomas Kiviaho
> Attachments: CheckDependencySnapshotsPhaseTest.testAllowTimestampedParent.patch
>
>
> Parent version could also be referenced by unique version number (assuming allowance to be set).
> Problems arise when such parent is resolved to a file containing -SNAPSHOT marker instead of unique version number. See <http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-7-SNAPSHOT/maven-release-plugin-2.0-beta-7-20070531.213659-1.pom>
> Reason is that whilst original model parent has the unique version artifact version is used instead.
> There are uniquely versioned artifacts as well which (I assume) avoid the problem
> See <http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-7-SNAPSHOT/maven-release-plugin-2.0-beta-7-20070726.151817-2.pom>
--
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