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
