Hello Steve,
you just found out about the ivy task deliver.
This task prepares the ivy.xml which gets published.
this is a snip from a build file of mine :
<mkdir dir="delivery"/>
<ivy:deliver deliverpattern="delivery/ivy.xml"
pubrevision="${revision}"
/>
<ivy:publish
artifactspattern="${websphere.lib.dir}/[artifact].[ext]"
srcivypattern="delivery/ivy.xml"
resolver="thirdparty"
pubrevision="${revision}"
status="release" overwrite="true"
/>
so I explicitly invoke this ivy:deliver task and feed the location of the ivy
file that deliver generates in the srcivypattern attribute of ivy:publish. When
you do not use the srcivypattern attribute, ivy:publish delegates to
ivy:deliver. The generated ivy file seems to go to the directory of the
artifact that you publish.
bonjour de la grande pomme,
Antoine
-------- Original-Nachricht --------
Datum: Fri, 10 Nov 2006 12:24:49 +0000
Von: Steve Loughran <[EMAIL PROTECTED]>
An: [email protected]
Betreff: Re: publishing war files
>
> No, I fixed it. I had to delete the ivy xml file created in dist/ next
> to the WAR and the rebuild would recreate it...it looks like ivy doesnt
> recreate this file if the source ivy.xml file has changed.
