Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
None
-
None
-
None
Description
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 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.