You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/07/24 14:40:22 UTC
[jira] Closed: (MRM-125) make discovery only discover new artifacts
[ http://jira.codehaus.org/browse/MRM-125?page=all ]
Brett Porter closed MRM-125.
----------------------------
Resolution: Fixed
> make discovery only discover new artifacts
> ------------------------------------------
>
> Key: MRM-125
> URL: http://jira.codehaus.org/browse/MRM-125
> Project: Maven Repository Manager
> Issue Type: Bug
> Components: discovery
> Reporter: Brett Porter
> Assigned To: Brett Porter
> Fix For: 1.0-beta-1
>
> Original Estimate: 3 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> currently every artifact is discovered every time. A technique that facilitates only finding new artifacts is needed.
> Note gotchas:
> - different operations will run at different times, so there can't be a single repository discovery timestamp. For example, indexing might check based on the last time the index was updated
> - some operations are not atomic (eg indexing may not complete, but the index is newer than some artifacts created afterwards, and artifacts created between discovery and indexing will fall through the cracks)
> I'd suggest narrowing down the times to some atomic operations (eg, updating index for all new artifacts, where index is only written at the end), and tracking the timestamp based on the conclusion of discovery, not the operation, then recording those timestamps in a metadata file in the root of the repository.
--
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