[
https://issues.apache.org/jira/browse/MRELEASE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-277.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Unique versioned snapshots allowance not covering always parent
> ---------------------------------------------------------------
>
> Key: MRELEASE-277
> URL: https://issues.apache.org/jira/browse/MRELEASE-277
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
