You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Archie Cobbs (JIRA)" <ji...@apache.org> on 2008/12/10 17:40:44 UTC

[jira] Created: (IVY-985) Packager resolver errors in the nested ant invocation are ignored by outer ant invocation

Packager resolver errors in the nested ant invocation are ignored by outer ant invocation
-----------------------------------------------------------------------------------------

                 Key: IVY-985
                 URL: https://issues.apache.org/jira/browse/IVY-985
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0-RC2
         Environment: openSUSE 11.0
            Reporter: Archie Cobbs


When resolving artifacts using the packager resolver, errors in the nested ant invocation are ignored by the outer ant invocation.

How to reproduce this problem:

# Check out {{http://ivyroundup.googlecode.com/svn/trunk}} and verify the prerequisites listed [here|http://code.google.com/p/ivyroundup/wiki/HowToBuildNormalRepository].
# Edit {{repo/modules/org.testng/testng/packager.xml}}, changing the SHA1 checksum to a different value
# Run {{ant -Dresolve.mod=testng clean resolve}}
# The packager resolver will download {{testng-5.7.zip}} and then attempt to verify the checksum
# The checksum verification will fail and an exception will be thrown, causing the nested packager resolver ant invocation (which is trying to resolve the jar artifact) to fail
# *Yet the outer ant invocation continues*, ignoring the error
# {{testng-5.7.zip}} will be downloaded (and fail checksum) two more times as ivy attempts to resolve the source and javadoc artifacts

*Note:* this bug may have the same underlying cause as [IVY-984|https://issues.apache.org/jira/browse/IVY-984].


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (IVY-985) Packager resolver errors in the nested ant invocation are ignored by outer ant invocation

Posted by "Archie Cobbs (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Archie Cobbs resolved IVY-985.
------------------------------

    Resolution: Invalid

After further testing I think this is actually correct behavior. Ivy will try to resolve everything, ignoring errors, until it finishes. Eventually the build does in fact fail.



> Packager resolver errors in the nested ant invocation are ignored by outer ant invocation
> -----------------------------------------------------------------------------------------
>
>                 Key: IVY-985
>                 URL: https://issues.apache.org/jira/browse/IVY-985
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-RC2
>         Environment: openSUSE 11.0
>            Reporter: Archie Cobbs
>
> When resolving artifacts using the packager resolver, errors in the nested ant invocation are ignored by the outer ant invocation.
> How to reproduce this problem:
> # Check out {{http://ivyroundup.googlecode.com/svn/trunk}} and verify the prerequisites listed [here|http://code.google.com/p/ivyroundup/wiki/HowToBuildNormalRepository].
> # Edit {{repo/modules/org.testng/testng/packager.xml}}, changing the SHA1 checksum to a different value
> # Run {{ant -Dresolve.mod=testng clean resolve}}
> # The packager resolver will download {{testng-5.7.zip}} and then attempt to verify the checksum
> # The checksum verification will fail and an exception will be thrown, causing the nested packager resolver ant invocation (which is trying to resolve the jar artifact) to fail
> # *Yet the outer ant invocation continues*, ignoring the error
> # {{testng-5.7.zip}} will be downloaded (and fail checksum) two more times as ivy attempts to resolve the source and javadoc artifacts
> *Note:* this bug may have the same underlying cause as [IVY-984|https://issues.apache.org/jira/browse/IVY-984].

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.