Each repository should have it's own consumer list

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.1.1
  • Fix Version/s: Backlog
  • Component/s: Design
  • Labels:
    None

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

This might be a documentation issue... the purge feature only applies to snapshots.

Show
Wendy Smoak added a comment - This might be a documentation issue... the purge feature only applies to snapshots.
Hide
Permalink
Brett Porter added a comment -

it should be noted that releases are never purged.

The problem is not per-repository purge settings (which we have), but the ability to configure different consumers per repository, and to have a default set for those that aren't unique.

Show
Brett Porter added a comment - it should be noted that releases are never purged. The problem is not per-repository purge settings (which we have), but the ability to configure different consumers per repository, and to have a default set for those that aren't unique.
Hide
Permalink
EJ Ciramella added a comment -

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.

Show
EJ Ciramella added a comment - 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.

People

  • Assignee:
    Unassigned
    Reporter:
    EJ Ciramella
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: