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 2008/06/13 04:34:12 UTC
[jira] Updated: (MNG-3470) Build does not fail on corrupted POM
even with checksumPolicy=fail
[ http://jira.codehaus.org/browse/MNG-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3470:
------------------------------
Fix Version/s: 2.0.x
> Build does not fail on corrupted POM even with checksumPolicy=fail
> ------------------------------------------------------------------
>
> Key: MNG-3470
> URL: http://jira.codehaus.org/browse/MNG-3470
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Benjamin Bentmann
> Priority: Minor
> Fix For: 2.0.x
>
> Attachments: mng-3470-it.patch
>
>
> If a dependency has a corrupted POM and the corresponding remote repo is configured with checksumPolicy=fail, Maven does still not fail the build.
> This seems to caused by the fix for MNG-2282: The original ChecksumFailedException is wrapped into a TransferFailedException which is errorneously converted into a ResourceDoesNotExistException by DefaultWagonManager.getArtifact(). Next up, DefaultArtifactResolver.resolve() wraps this into an ArtifactNotFoundException. DefaultMavenProjectBuilder.findModelFromRepository() will catch this and simply create a stub POM instead of failing.
> The code from the trunk looks different, not sure if it suffers from this. Now that I have a JIRA id, I will try to setup an IT.
--
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