ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mitch Gitman" <>
Subject buildnumber Ant task & automated updates of ivy.xml
Date Wed, 19 Nov 2008 16:12:38 GMT
There's one Ivy Ant task that had been flying under my radar, the
buildnumber <>task.

It seems to me that the natural use for the *buildnumber *task is during a
build invoked by continuous integration. A CI-invoked Ant target would go
into an ivy.xml file and update the /ivy-module/info@revision attribute with
the property value obtained from *buildnumber*. This could
come into play when, under "Dealing with integration versions" on the the Ivy
Best Practices page<>,
you take the "create automatically a new version for each" approach.

I'd be interested in hearing what other uses folks have found for the

Also (and actually this has nothing particularly to do with *buildnumber*),
I'd be interested in hearing what mechanisms folks are doing for doing an
automated update of ivy.xml files. Besides the
/ivy-module/info@revision attribute,
there's the /ivy-module/dependencies/dependency@rev attribute, which also
can be a good candidate for automated updates in certain situations.

I can think of two ways of automatically updating the content of an ivy.xml

   - Use regular expressions. Advantage: everything's right there in the
   build.xml. Disadvantage: regular expressions. Yuck!
   - Manipulate the XML programmatically, such as by binding Java objects to
   the XML schema. This has the disadvantage of requiring Java code (and
   possibly an additional library not already in the classpath), so you'd have
   to create a separate Ant task or Java executable.

Or is there some other mechanism already out there in some Ant task (Ivy or
non-Ivy) that I'm missing, like I'd missed the *buildnumber *task for a

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message