Re: Repository purge (MRM-294 and MRM-275)
Brett Porter wrote: On 25/07/2007, at 8:54 PM, Maria Odea Ching wrote: 3. artifact count to be retained is this within the given version? ie, keep X builds of this snapshot. I think this would be specified for all snapshots, not per version. It would be a long list if it would be for each version. Sorry, I must have misunderstood what you meant. So you mean, if the number kept is 5, then it would keep 5 in total of the latest, no matter how many versions there are? - Brett Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. Thanks, Deng
Re: Repository purge (MRM-294 and MRM-275)
On 25/07/2007, at 9:09 PM, Maria Odea Ching wrote: Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. I think we're saying the same thing - can you just clarify for me are you saying 5 are: a) 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT, 1.4-SNAPSHOT, 1.5- SNAPSHOT; or b) 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3, 1.1-20070506.121113-4, 1.1-20070506.121113-5 I was thinking it's (b), since (a) is taken care of by the delete anything that's released rule. Cheers, Brett
Re: Repository purge (MRM-294 and MRM-275)
On 7/25/07, Maria Odea Ching [EMAIL PROTECTED] wrote: I'm trying to fix up MRM-294, and I need your input/comments :-) Should the configuration for the repository purge be for each repository? If so, I think it can be consolidated with the repository scanning schedule and set up as another consumer which would be executed during repository scanning. I think you and Brett have worked out the details, so I just want to confirm that this will be configurable in archiva.xml prior to starting the app. -- Wendy
Re: Repository purge (MRM-294 and MRM-275)
Wendy Smoak wrote: On 7/25/07, Maria Odea Ching [EMAIL PROTECTED] wrote: I'm trying to fix up MRM-294, and I need your input/comments :-) Should the configuration for the repository purge be for each repository? If so, I think it can be consolidated with the repository scanning schedule and set up as another consumer which would be executed during repository scanning. I think you and Brett have worked out the details, so I just want to confirm that this will be configurable in archiva.xml prior to starting the app. Yep, it'll be configurable in archiva.xml :) Thanks, Deng
Re: Repository purge (MRM-294 and MRM-275)
Yep, I'm also saying (b) :) Thanks, Deng Brett Porter wrote: On 25/07/2007, at 9:09 PM, Maria Odea Ching wrote: Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. I think we're saying the same thing - can you just clarify for me are you saying 5 are: a) 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT, 1.4-SNAPSHOT, 1.5-SNAPSHOT; or b) 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3, 1.1-20070506.121113-4, 1.1-20070506.121113-5 I was thinking it's (b), since (a) is taken care of by the delete anything that's released rule. Cheers, Brett