ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Woods <>
Subject Buildnumber task - no way to specify resolver
Date Tue, 03 Mar 2009 15:56:33 GMT

First off, I just want to thank the development team for such a cool tool. My
experience with Ivy has been great so far.

I'm having an issue right now regarding publishing to local and shared
repositories. My question is, is there any specific reason why I can't
specify which resolver to use when determining buildnumbers(ant task
ivy:buildnumber)? I understand that the resolver used is the one that is set
to "default". Is there a way to change it so I can use the "main" resolver
chain instead (and therefore ignore any artifacts that happen to be in the
local repository)?

In my situation, developer "Fred" publishes artifacts to his local
repository for day to day changes (say versions fred.1, fred.2, fred.3,
etc). When he is ready to release something,  I want the build number to be
the next version after whats already in the shared repository (say version
1.4.2,  where 1.4.1 is already in the shared repository). Unfortunately,
instead of version 1.4.2 being published, fred.4 is being published instead
because local is in the "default" resolver chain.

I understand I could specify a different ivysettings.xml file (where the
only difference is that the default resolver is "main" instead of
"default"), or I could just clean out the local cache - but those solutions
are seem unnecessarily inconvenient. Is there another strategy I should try?
Is this a feature that could be added in the future?
View this message in context:
Sent from the ivy-user mailing list archive at

View raw message