Delete Released Snaphots

[Deng Ching-2]

Hi,

I'll be working on http://jira.codehaus.org/browse/MRM-797, and it has been
discussed in the jira
that the delete released snapshots capability should be ran against other
repositories. The current
implementation of this feature is it just looks in the repo itself for
released versions and deletes the
snapshot version if a released version of it is found.

I made some drafts on how to fix this issue:
Option 1: No UI configuration. Just get the other repositories the user has
access to and check
     against all of them for a released version of the snapshot.

Option 2: With UI configuration:
    - Add a drop down box that would list the repos (which the user can
access) and the user
      can pick from these repos. Selected repo will be listed with a 'X'
icon on the right side for Delete,
      like what we have for the blacklist/whitelist patterns in the Proxy
Connector page.
   - Update CleanupReleasedSnapshotsRepositoryPurge to get the repos which
the cleanup would be
      executed against.
   - Update the configuration model to look like this:
         <releasedSnapshotsCleanup>
           <deleteReleasedSnapshots>true</deleteReleasedSnapshots>
           <repositories>
             <repositoryId>snapshots</repositoryId>
             ....
           </repositories>
         </releasedSnapshotsCleanup>

Thoughts anyone? :-)


Thanks,
Deng

[Arnaud HERITIER]

The problem I see is that we can't easily know when the purge is executed
for a given snapshot if the release which is in another repository is also
available for all users having access to the snapshot.
I think it can be a headache If we try to fix this, and it adds very few
value because, often, users who have access to snapshots have also access to
releases (or the configuration is very weird).
I propose that we do something as simple as possible.
We just check for a snapshot if the release exist in another repository and
if it is true we remove it.
No more UI settings...

Arnaud

On Wed, May 14, 2008 at 8:43 AM, Maria Odea Ching <oching@...> wrote:

> Hi,
>
> I'll be working on http://jira.codehaus.org/browse/MRM-797, and it has
> been
> discussed in the jira
> that the delete released snapshots capability should be ran against other
> repositories. The current
> implementation of this feature is it just looks in the repo itself for
> released versions and deletes the
> snapshot version if a released version of it is found.
>
> I made some drafts on how to fix this issue:
> Option 1: No UI configuration. Just get the other repositories the user
> has
> access to and check
>     against all of them for a released version of the snapshot.
>
> Option 2: With UI configuration:
>    - Add a drop down box that would list the repos (which the user can
> access) and the user
>      can pick from these repos. Selected repo will be listed with a 'X'
> icon on the right side for Delete,
>      like what we have for the blacklist/whitelist patterns in the Proxy
> Connector page.
>   - Update CleanupReleasedSnapshotsRepositoryPurge to get the repos which
> the cleanup would be
>      executed against.
>   - Update the configuration model to look like this:
>         <releasedSnapshotsCleanup>
>           <deleteReleasedSnapshots>true</deleteReleasedSnapshots>
>           <repositories>
>             <repositoryId>snapshots</repositoryId>
>             ....
>           </repositories>
>         </releasedSnapshotsCleanup>
>
> Thoughts anyone? :-)
>
>
> Thanks,
> Deng
>

[Deng Ching-2]

Ok, agreed.. :-)

Thanks,
Deng

On Wed, May 14, 2008 at 4:18 PM, Arnaud HERITIER <aheritier@...>
wrote:

> The problem I see is that we can't easily know when the purge is executed
> for a given snapshot if the release which is in another repository is also
> available for all users having access to the snapshot.
> I think it can be a headache If we try to fix this, and it adds very few
> value because, often, users who have access to snapshots have also access
> to
> releases (or the configuration is very weird).
> I propose that we do something as simple as possible.
> We just check for a snapshot if the release exist in another repository
> and
> if it is true we remove it.
> No more UI settings...
>
> Arnaud
>
> On Wed, May 14, 2008 at 8:43 AM, Maria Odea Ching <oching@...>
> wrote:
>
> > Hi,
> >
> > I'll be working on http://jira.codehaus.org/browse/MRM-797, and it has
> > been
> > discussed in the jira
> > that the delete released snapshots capability should be ran against
> other
> > repositories. The current
> > implementation of this feature is it just looks in the repo itself for
> > released versions and deletes the
> > snapshot version if a released version of it is found.
> >
> > I made some drafts on how to fix this issue:
> > Option 1: No UI configuration. Just get the other repositories the user
> > has
> > access to and check
> >     against all of them for a released version of the snapshot.
> >
> > Option 2: With UI configuration:
> >    - Add a drop down box that would list the repos (which the user can
> > access) and the user
> >      can pick from these repos. Selected repo will be listed with a 'X'
> > icon on the right side for Delete,
> >      like what we have for the blacklist/whitelist patterns in the Proxy
> > Connector page.
> >   - Update CleanupReleasedSnapshotsRepositoryPurge to get the repos
> which
> > the cleanup would be
> >      executed against.
> >   - Update the configuration model to look like this:
> >         <releasedSnapshotsCleanup>
> >           <deleteReleasedSnapshots>true</deleteReleasedSnapshots>
> >           <repositories>
> >             <repositoryId>snapshots</repositoryId>
> >             ....
> >           </repositories>
> >         </releasedSnapshotsCleanup>
> >
> > Thoughts anyone? :-)
> >
> >
> > Thanks,
> > Deng
> >
>