Good day to you, Brett, Sorry, but i'm just starting with it right now. Something came up a few days ago that needed my immediate attention. Anyway, i'll try to give an estimate tom.
Thanks, Franz On 9/4/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I'll leave -77 to last, but I'm starting work on this. So I'll do -83 and some backend stuff (-161, -162), as well as -143 and maybe -82. Basically what I'm thinking is that there will be a component - the reporting manager, that: * is the central place to log issues that occur outside of general reporting (eg, the indexer can find problems that reports wouldn't) * tracks all the issues, and persists them to disk at the root of the repository, loading them back up on startup * executes reports when asked on a schedule and controls what reports are available Let me know if you've made any progress! Cheers, Brett On 01/09/2006, at 6:35 PM, Franz Allan Valencia See wrote: > On 8/31/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> >> On 01/09/2006, at 12:54 AM, Franz Allan Valencia See wrote: >> >> > Good day to you, Brett, >> > >> >> There's lot of things to be done. >> >> >> >> - implement triggering of the reports and recording of the results >> > >> > do we now have designs on what events triggers what actions? ^_^ >> >> The triggering at present is all time based - the scheduler will kick >> off a task which scans the repo and checks for a set of issues (in >> the same way as the indexing works, basically). >> >> However, I think this is a dependant task to do first: >> - MRM-83 (change the reports to take a listener) >> >> > >> >> - implement the web actions for those screens >> > >> > by "those screens" are you referring to the repoman-site itself? or >> > just the reports.html...if it's just reports.html, which web >> actions >> > were you referring to? >> >> They aren't obvious because of the link colouring, but there's a >> "repair" link in some cases. It should also be possible to navigate >> to the artifact and possibly other actions. >> >> > >> >> - implement ways to quick fix problems found in the reports >> > >> > Absolutely no idea as to what you have in mind for this ^_^ >> >> I think a report should have these methods: >> >> boolean canQuickFix( Result result ); >> void performQuickFix( Result result ); >> >> So, for example, if the checksum is incorrect, this can be fixed for >> any file by recalculating and saving the checksum. >> >> > >> >> >> >> Any in particular that you are interested in? >> >> >> >> Cheers, >> >> Brett >> >> >> > >> > Currently, my interests are leaning towards the triggers ^_^ >> >> That should be fairly straightforward to set up so its a good place >> to start. Thanks! >> >> > >> > Thanks a bunch, >> > Franz >> > > > Since, the first one depends on MRM-83 (and someone already took > responsibility in it), i guess i'll start first with the > implementation of the web actions ^_^ > > btw, when one navigates to the other artifacts, what should be seen, > the [1] page, or something like [2] or what? ^_^ > > Sorry if i have too many questions. I am interested in working with > archiva, but i only know a small amount about it. btw, where can i see > the details regarding this project, i mean, where it's heading and > where it is right now ^_^ > > Thanks a bunch, > Franz > > [1] http://people.apache.org/~brett/repoman-site/artifact.html > [2] http://snapshots.repository.codehaus.org/
