Hi there, <ivy:deliver> is used to generate the ivy.xml before publication based on the last resolved informations.
Why are we generating an ivy.xml here ? Because when publishing, ivy adds some attributes in the generated ivy.xml file (like publication date, publication revision, publication branch). One other goal of the <ivy:deliver> is to replace dynamic revisions in project dependencies (if you use latest.revision, or [2.2.+[ or stuff like that in your <dependencies>). To sum up <ivy:deliver> fixes every dynamic value in the ivy.xml file to make it reproducible. <ivy:publish> can make the <deliver> process if you haven't do it explictly before. So you can consider <ivy:deliver> as optionnal. In some cases, invoking explicitly <ivy:deliver> is required : - If you want to do some post processing on ivy.xml file before publishing - If you're using recursive delivery HTH 2010/10/8 Stefan Bodewig <bode...@apache.org> > Hi, > > I have one issue that is slowly bubbling up on my TODO list: I promised > to provide Ant+Ivy content for > <http://www.apache.org/dev/publishing-maven-artifacts.html> > > Rather than starting a lengthy thread on this list, I've created a Wiki > page <http://wiki.apache.org/ant/PublishingMavenArtifactsWithAntAndIvy> > > Please review what I've written, in particular the Ivy specific parts > since I'm really a newbie when it comes to Ivy. If anybody could > explain to me why we use the deliver task at all, I'd be grateful. > > Thanks > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > -- Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org
