ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Borrmann <>
Subject Maintaining a shared repository
Date Mon, 16 Mar 2009 14:58:07 GMT

does anybody have an idea how to handle the following maintenace use case 
- or am I trying to do something terribly stupid...

Replace version for a module with a artifact having a different name
Our (file system based) repository contains a module orgName.moduleName 
with version 1.0.0. It is realized by artifact 
orgName.moduleName_1.0.0.jar. Now we need to publish a fix to the 
repository which has a different name, e.g. patch_1.0.0.jar. Is there a 
defined way to do this? I tried the following solutions:
a) force=false and overwrite=false
In this case an error is generated and the ivy.xml file in the repository 
is not changed (still points to orgName.moduleName_1.0.0.jar). But 
patch_1.0.0.jar is still copied to the repository and left there as an 
orphan with no referring ivy.xml file.
b) force=true and overwrite=true
The ivy.xml file in the repository is changed. Therefore our patch is 
used. But the original artifact file (and its checksums) are left as 

Is there an automated way of getting rid of these orphans?

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