Re: Release management
Wendy Smoak wrote: On 7/19/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: I know I'm interested :-) Thanks for the links Wendy! Okay, take a look at that info... I know you've worked with Continuum release and the release plugin in general, so the first administrative detail is probably generating your signing key. I can be a co-release manager if you want. I'd be happy to :) Thanks Wendy! -Deng
Re: [Reporting] UI via JasperReports
Hi Guys, I've attached a couple of patches for this on MRM-329. :) Comments are very much welcome... -Teody Maria Odea Ching wrote: I don't really know about its licensing though.. -Deng Brett Porter wrote: "Me too" - 2 years ago, I did both the html paging, and emailing pdfs of the same thing, plus letting people write their own reports to run. how does the licensing fit these days? On 19/07/2007, at 12:53 PM, Maria Odea Ching wrote: I had some experience with JasperReports and iReport. I'll be happy to help out, though I may have to polish up on that. It's been 2 years since I last used it. -Deng Joakim Erdfelt wrote: I'm about to integrate JasperReports into archiva for report presentation in archiva. This will be a learning experience for me. I'd love to have some help with this effort. Anyone here have any experience with JasperReports on webapps? (things like HTML output with paging) - Joakim
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)
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)
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 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
Re: Repository purge (MRM-294 and MRM-275)
Brett Porter wrote: On 25/07/2007, at 7:50 PM, Maria Odea Ching wrote: Hi Everyone, I'm trying to fix up MRM-294, and I need your input/comments :-) Cool, this will be a popular feature :) 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. Definitely per repository for the configuration - and I think tying it to the scanning schedule and using a consumer makes the most sense, sure. I've also identified the fields which can be configured by the user (from MRM-294 and MRM-275): 1. schedule of THE PURGE (this is the repo scanning schedule if per repository) 2. timestamp basis of which snapshots will be deleted -- specific date/timestamp (e.g. all builds older than 01/01/07) OR time based (e.g. any builds order than 1 month) I think only the latter option is needed here? Not sure when I'd use a specific date. Also - I'd like any artifacts that are not in active development to be deleted entirely (eg, 1.0-SNAPSHOT when 1.0 is released). Yeah, good thing you brought it up :) I didn't consider those artifacts. 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. In the configuration page, the user can choose which criteria to use for the repo purge (either #2 or #3 in the list above). Also for #2, I thought to provide the user the option to choose from these: - specific date/timestamp - by # of months - by # of days - by # of years I'd go simple here - maybe have anything older than X days OR keep Y builds. Thanks! Cheers, Brett Thanks, Deng
Re: Repository purge (MRM-294 and MRM-275)
On 25/07/2007, at 7:50 PM, Maria Odea Ching wrote: Hi Everyone, I'm trying to fix up MRM-294, and I need your input/comments :-) Cool, this will be a popular feature :) 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. Definitely per repository for the configuration - and I think tying it to the scanning schedule and using a consumer makes the most sense, sure. I've also identified the fields which can be configured by the user (from MRM-294 and MRM-275): 1. schedule of THE PURGE (this is the repo scanning schedule if per repository) 2. timestamp basis of which snapshots will be deleted -- specific date/timestamp (e.g. all builds older than 01/01/07) OR time based (e.g. any builds order than 1 month) I think only the latter option is needed here? Not sure when I'd use a specific date. Also - I'd like any artifacts that are not in active development to be deleted entirely (eg, 1.0-SNAPSHOT when 1.0 is released). 3. artifact count to be retained is this within the given version? ie, keep X builds of this snapshot. In the configuration page, the user can choose which criteria to use for the repo purge (either #2 or #3 in the list above). Also for #2, I thought to provide the user the option to choose from these: - specific date/timestamp - by # of months - by # of days - by # of years I'd go simple here - maybe have anything older than X days OR keep Y builds. Thanks! Cheers, Brett
Repository purge (MRM-294 and MRM-275)
Hi Everyone, 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've also identified the fields which can be configured by the user (from MRM-294 and MRM-275): 1. schedule of THE PURGE (this is the repo scanning schedule if per repository) 2. timestamp basis of which snapshots will be deleted -- specific date/timestamp (e.g. all builds older than 01/01/07) OR time based (e.g. any builds order than 1 month) 3. artifact count to be retained In the configuration page, the user can choose which criteria to use for the repo purge (either #2 or #3 in the list above). Also for #2, I thought to provide the user the option to choose from these: - specific date/timestamp - by # of months - by # of days - by # of years Thoughts anyone? Anyway, that's all for now.. thanks in advance! :) -Deng
