I think the expected behavior is to have an implicit delivery triggered when the resolved ivy file doesn't exist (or always if forcedeliver is set to true true). So, I think you can raise an issue, yes (and, why not, provide a patch :-)
2008/8/12 Brown, Carlton <[EMAIL PROTECTED]>: > Now I'm noticing that implicit delivery is not performed by ivy:publish > if srcivypattern is true, not even if forcedeliver is set to true. > > Is this expected behavior? Should I open a JIRA on it? > > -----Original Message----- > From: Gilles Scokart [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2008 3:20 AM > To: [email protected] > Subject: Re: Publish is somehow disrupted by presence of ivy report? > > The publish implicitely call a deliver if required. When the delivered > ivy file already exist, no deliver is done, so you are still trying to > publish the old delivered ivy file (that contains a reference to the two > jars). > > You can change this behavior by setting forcedeliver in you publish > task. > > > > 2008/8/8 Brown, Carlton <[EMAIL PROTECTED]>: >> Actually on second inspection it appears it's the presence of the >> ivy.xml in the publish dir that is affecting this behavior... But is >> that how it's supposed to work? >> >> -----Original Message----- >> From: Brown, Carlton [mailto:[EMAIL PROTECTED] >> Sent: Friday, August 08, 2008 10:05 AM >> To: [email protected] >> Subject: Publish is somehow disrupted by presence of ivy report? >> >> I have noticed that if I publish an ivy report (as ivy-report.html) as > >> an artifact of a module, it seems to interfere with caching somehow. >> >> For example, steps to reproduce: >> 1: Create ivy.xml that specifies the publication of a 2 jars and an >> ivy-report.html file (created by ivy:report) >> 2: Resolve and publish >> 3: Change the ivy.xml and remove the reference to one of the jar > files. >> Also remove that jar from the publish dir that is referenced by the >> artifacts pattern >> 4: Attempt to resolve and publish. 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. Publish still >> fails for the same reason. This failure should not occur. >> 6: Remove ivy-report.html from the publish dir. >> 7: Attempt to resolve and publish. Success. >> >> Is my test flawed somehow, or is Ivy implicitly using an ivy report >> for resolution information? It seems very strange. >> >> Thanks, >> Carlton >> >> >> >> ----------------------------------------- >> ==================================================== >> This message contains PRIVILEGED and CONFIDENTIAL information that is >> intended only for use by the named recipient. If you are not the named > >> recipient, any disclosure, dissemination, or action based on the >> contents of this message is prohibited. In such case please notify us >> and destroy and delete all copies of this transmission. Thank you. >> ==================================================== >> > > > > -- > Gilles Scokart > -- Gilles Scokart
