[
https://jira.codehaus.org/browse/MRM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320454#comment-320454
]
Olivier Lamy commented on MRM-1749:
-----------------------------------
You mean 1.0.0.BUILD-SNAPSHOT will be release as 1.0.0.RELEASE ?
If that's the case, snapshots won't be deleted as the released version must be
1.0.0.BUILD .
Maven itself will consider this versionning model.
> 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
