[
https://jira.codehaus.org/browse/MRM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320580#comment-320580
]
Alexander Franken commented on MRM-1749:
----------------------------------------
Yes, 1.0.0.BUILD-SNAPSHOT is released as 1.0.0.RELEASE. There are a handful of
sources that indicate that Maven 3 was intended to support an alternate more
flexible model. However, finding something concrete and definitive is a
challenge.
So, the Maven versions plugins states the following:
{quote}
The versions-maven-plugin knows three rules for comparing version numbers:
maven
The standard Maven 2.x version numbering scheme.
mercury
The "new" version numbering scheme used by the Maven Mercury.
numeric
An alternative version numbering scheme, similar to mercury but with no
"special" qualifiers.
{quote}
I believe our versioning scheme, again modeled after Spring Framework (which
was modeled based on OSGI conventions), is most closely related to the "new
Mercury" versioning scheme.
http://docs.codehaus.org/display/MAVEN/Mercury+Version+Ranges
Long store short, I found some evidence from Spring references that Artifactory
has the same problem. I tracked down the following page that indicates that
Artifactory intends to add support for, "Support for flexible non-Maven
snapshot and release identification will be introduced in the upcoming release
of Artifactory".
http://wiki.jfrog.org/confluence/display/RTF/Local+and+Remote+Repositories
Can you do something to support this version scheme? Could you also provide
insight into (or point me to) the logic you use to determine "released
snapshots"? Thanks.
> Delete Released Snapshots Not Working / Expectations?
> -----------------------------------------------------
>
> Key: MRM-1749
> URL: https://jira.codehaus.org/browse/MRM-1749
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3.5, 1.4-M3
> Reporter: Alexander Franken
>
> We have two managed repos (internal & snapshots). Both have been marked with
> "Delete released snapshots". As you would expect, we do not allow snapshots
> in in "internal" and no releases in "snapshots". We also use proxy
> connectors. I have tried both 1.3.5 & 1.4-M3 without luck.
> I'm wondering if logic requires pre-M3 version conventions (i.e. 1.3-SNAPSHOT
> & 1.3-RELEASE). We use a variation which I thought was supported in Maven 3.
> For example, 1.0.0.BUILD-SNAPSHOT & 1.0.0.RELEASE. Could this be the issue?
> Can someone provide any detail on the logic used for this feature? A little
> more about the M3 version changes
> http://docs.codehaus.org/display/MAVEN/Versioning. This particular
> convention was modeled after the Spring Framework (and related Spring
> projects).
> Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
