On Wed, 2005-07-06 at 09:05 +0200, Torsten Curdt wrote: > >>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 > > ;-)
there's a possibility that this won't work. someone might need to talk to the maven folks since i believe that ibiblio has non-deletion policies which may prevented this. it's possible the bad jar got in there through the java repository (http://www.apache.org/dist/java-repository/commons-cli/jars/ i think contains a different 1.0 jar to http://www.apache.org/dist/jakarta/commons/cli/binaries/.) should we ask the java repo team? but +1 to actively pushing a fix out however it's done... - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
