[
http://jira.codehaus.org/browse/MRM-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRM-776.
----------------------------
Resolution: Duplicate
Fix Version/s: (was: 1.4)
Assignee: Brett Porter
without more details I'm not sure of the circumstances that would have brought
this about, but detecting artifact deletions per MRM-999 should take care of
this.
> Clean up report data
> --------------------
>
> Key: MRM-776
> URL: http://jira.codehaus.org/browse/MRM-776
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.0.2
> Environment: Maven version: 2.0.8
> Java version: 1.6.0_05
> OS name: "linux" version: "2.6.22.17-0.1-bigsmp" arch: "i386" Family: "unix"
> Reporter: Roland Klein
> Assignee: Brett Porter
> Priority: Minor
>
> The problem was, after an upgrade there were outdated data in the db and this
> leads to errorneous report.
> Suggestions
> a) synchronize the db with the filesystem. could be long running task and not
> trivial to implement.
> b) just delete the report data and collect them again. could be long running
> task, but functionality is already there
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
