[
http://jira.codehaus.org/browse/MRM-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146496#action_146496
]
EJ Ciramella commented on MRM-930:
----------------------------------
Brett's right, but I can't pass on Wendy's comment.
How does Archiva determine a snapshot? Is it because it has found a "SNAPSHOT"
in the path leading up to an artifact? Is it because the pom for that artifact
has "1.0-SNAPSHOT" listed as its version?
We've bent the rules here a bit and the answer will effect how purging is
looked at.
> Each repository should have it's own consumer list
> --------------------------------------------------
>
> Key: MRM-930
> URL: http://jira.codehaus.org/browse/MRM-930
> Project: Archiva
> Issue Type: Improvement
> Components: design
> Affects Versions: 1.1.1
> Reporter: EJ Ciramella
>
> I'm unable to NOT purge one repository AND have the purge feature turned on
> in another.
> Each repository should have its own set of configuration versus a shared one.
> I'm talking about the "repository scanning" menu option.
> Say we have a snapshot repository and a release repository. Some artifacts
> like our cryptography builds change once ever few years (and that isn't set
> in stone). I'd like to have the snapshot repository purged every month but
> can't turn on the purge feature in the repository scanning menu without
> archiva deleting stuff out of the release repository.
--
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
