You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/03/03 18:32:28 UTC
[jira] Reopened: (MNG-3421) artifacts not found in any repo are
continually rechecked in subsequent builds
[ http://jira.codehaus.org/browse/MNG-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey reopened MNG-3421:
-----------------------------
resolver-status.properties file created in the first patch for this issue aggregates multiple artifact versions into a single file, making it difficult to manage transitions for a given artifact version when it becomes available again.
I have a new patch file to apply, that corrects this by using a separate resolver-status.properties file for each artifact id (includes version), and will remove the resolver-status.properties file when the artifact becomes available.
> artifacts not found in any repo are continually rechecked in subsequent builds
> ------------------------------------------------------------------------------
>
> Key: MNG-3421
> URL: http://jira.codehaus.org/browse/MNG-3421
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.1-alpha-1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1-alpha-1
>
> Attachments: maven-artifact-c.diff, maven-artifact-d.patch
>
>
> During subsequent calls to Maven, artifacts that could not be found on any repository are continually rechecked.
> Need to track attempts to resolve artifacts with timestamps and make those attempts subject to updateInterval, not just found artifacts that may be stale.
> I'm attaching a patch sent to me by Igor Fedorenko, which I'll review and commit if appropriate.
--
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