ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Deleting previous JARs/revisions - avoiding duplicate JARs
Date Wed, 29 Apr 2009 13:35:59 GMT

What you actually want to do is at a synch=true on the ivy-retrieve ant
task (if you are pulling back jars that way), or click the "delete old
retrieved artifacts" checkbox if you are using the IvyDE from within

   >                                                    To 
             28/04/2009 11:04                                           cc 
             Please respond to         Deleting previous JARs/revisions -  
             ivy-user@ant.apac         avoiding duplicate JARs             

Hi all,

I've recently started using Ivy for a small 'core' package where I work
(that's your 'noob' flag). I really like what I've seen so far, but I'm
stumped on one thing: removal of previous JARs (i.e. revisions) when a
revision is available. For example, say I have my-lib.1.1.jar and I change
my ivy.xml to require 1.2, I would like the my-lib.1.1.jar to be

I *think* the conflict element in my ivy.xml (ref: should do
this for me, but the documentation is quite confusing and there are no
examples. Furthermore the default conflict manager is latest-revision which
is what I'd assume would be used, so I doubt there's any explicit
configuration needed. Regardless, my ivy:retrieve does not remove it and
left with duplicate JARs in my lib folder - something I really want to

Can anyone shed some light on what I'm missing please?

Many thanks,

Alex Collins

This email has been scanned for all viruses by the MessageLabs Email
Security System.

Target is a trading name of Target Group Limited, 
registered in England and Wales No. 1208137
Registered office:  Target House, Cowbridge Road East, Cardiff CF11 9AU

This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL. 
If you are not the intended recipient you must not copy, 
distribute or take any action or reliance upon it. 
The content of this message may also contain personal 
views of an employee of this company and does
not necessarily represent the view of the company.
This message has been scanned by Norton Anti-Virus. 
It has also been scanned by MAILsweeper to enforce our e-mail 
policy. If you have any concerns or comments about the content 
of this message, please  e-mail

This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit

View raw message