ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Eigenbrodt <martineigenbr...@googlemail.com>
Subject Re: Buildnumber task - no way to specify resolver
Date Wed, 04 Mar 2009 09:15:51 GMT
Please note there is an issue with buildnumber the  resovler attribute and
chained resolvers:
https://issues.apache.org/jira/browse/IVY-1037

Martin

2009/3/3 Stephen Woods <swoods123@gmail.com>

> Thanks for the quick reply... I'll take a look!
>
> On Tue, Mar 3, 2009 at 11:12 AM, Maarten Coene <maarten_coene@yahoo.com
> >wrote:
>
> > This has already been added in SVN trunk:
> > https://issues.apache.org/jira/browse/IVY-1019
> >
> > Could you give it a try?
> >
> > Maarten
> >
> >
> >
> >
> > ----- Original Message ----
> > From: Stephen Woods <swoods123@gmail.com>
> > To: ivy-user@ant.apache.org
> > Sent: Tuesday, March 3, 2009 4:56:33 PM
> > Subject: Buildnumber task - no way to specify resolver
> >
> >
> > 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:
> >
> http://www.nabble.com/Buildnumber-task---no-way-to-specify-resolver-tp22311412p22311412.html
> > Sent from the ivy-user mailing list archive at Nabble.com.
> >
> >
> >
> >
>

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