ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlton Brown (JIRA)" <j...@apache.org>
Subject [jira] Created: (IVY-954) ivy:publish calls an implicit resolve on its delivered ivy file
Date Tue, 21 Oct 2008 19:17:44 GMT
ivy:publish calls an implicit resolve on its delivered ivy file
---------------------------------------------------------------

                 Key: IVY-954
                 URL: https://issues.apache.org/jira/browse/IVY-954
             Project: Ivy
          Issue Type: Bug
    Affects Versions: 2.0-RC1, 2.0.0-beta-2
            Reporter: Carlton Brown


Steps to produce:

1:  Create ivy.xml that specifies the publication of 2 jars 
2:  Build jars, then resolve again.
3:  Change the ivy.xml and remove the reference to one of the jar files.   Also delete that
jar from the publish dir
4:  Attempt to resolve and publish.  An expected failure occurs, publish fails because the
removed jar is no longer in the publish dir.   Failure is expected, because the old ivy.xml
is still in cache.
5:  Clean ivycache.  Attempt to resolve and publish.   This time it publish should work, however
it still fails for the same reason because an implicit resolve is happening on the delivered
ivy.xml file
6:  Remove delivered ivy.xml from the published artifacts dir
7:  Attempt to resolve and publish.  Publish now works successfully.

The workaround is to set forcedeliver equal to true.   If publish is supposed to be a post-resolve
task (which makes sense), then it should not be doing implicit resolves on the delivered ivy
file that could potentially be different from the resolved ivy file.

I guess what I'm actually saying is that forcedeliver=false seems like a degenerate use case
and should not be allowed.

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


Mime
View raw message