You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2008/02/21 16:00:28 UTC
[jira] Created: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Transfer errors cause junk metadata in the local repo
-----------------------------------------------------
Key: MNG-3415
URL: http://jira.codehaus.org/browse/MNG-3415
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.0.8
Reporter: Brian Fox
I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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
[jira] Commented: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126548 ]
John Casey commented on MNG-3415:
---------------------------------
I have the fix in place on my localhost, but I'm still trying to nail down the integration tests and make them work in both 2.0.9 and 2.1. It'll be Monday before I get this sorted out.
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-3415.diff
>
>
> I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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
[jira] Updated: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3415:
---------------------------
Assignee: John Casey
Fix Version/s: 2.0.9
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
>
> I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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
[jira] Updated: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3415:
------------------------------
Attachment: MNG-3415.diff
no time to test it today - but I think this patch would resolve this issue
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-3415.diff
>
>
> I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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
[jira] Closed: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-3415.
---------------------------
Resolution: Fixed
This issue is fixed. I applied Brett's patch (thanks for the heavy lifting here, Brett), and added integration tests to check writing the metadata on ResourceNotFoundException, but not on TransferFailedException.
NOTE: This integration test required a little extra functionality in the abstract parent test class, to allow conditional use of different files for the updateInterval calculation (we're making sure these files are not modified on successive builds when ResourceNotFoundException happens).
The integration test should be fairly well-documented, so have a look.
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-3415.diff
>
>
> I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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
[jira] Commented: (MNG-3415) Transfer errors cause junk metadata in
the local repo
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126248 ]
Brett Porter commented on MNG-3415:
-----------------------------------
using MNG-3341's IT as a basis should make it pretty easy to reproduce (just use an invalid wagon to trigger the error). However, what really needs to be rechecked is that no other metadata operations break as a result (most particularly, you don't want to end up downloading missing metadata every time if it doesn't exist)
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-3415.diff
>
>
> I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.
--
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