>>I could take care of pushing out the jar to >>ibilio ...but I think we should have a proper >>release or at least a tag for 1.0.1 then. > > > Sorry, I don't understand this.
ibiblio# rm commons-cli-1.0.jar #scp commons-cli-1.0.jar minotaur #svn co https://.../CLI_1_0_1 #maven jar #scp commons-cli-1.0.1.jar minotaur ...sync ...sync ibiblio# ls commons-cli-1.0.jar <-- the real 1.0! commons-cli-1.0.1.jar ;-) > The filename "commons-cli-1.0.jar" is now ambiguous. It could refer to > either of two actual bunches of files. Updating the ibiblio one from the > bad jar to the good jar is therefore pretty pointless; the bad jar is > out there in circulation. Sure ...but there is not much we can do about it. Unfortunately maven will not update the jar. People have to remove it from their local .maven cache. ...so if it breaks a project - it only does on a fresh checkout. But IMHO this is our problem only to a limited extend. What would happen if one of the Apache mirrors would screw up like this ...what would we do? I think just let's fix it and make an announcement on users. WDYT? cheers -- Torsten
signature.asc
Description: OpenPGP digital signature
