> 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.
I just had a chat over at #maven at codehaus.org ...we could just update the jar in the apache repo and it should be synch'd with ibiblio. The apache repo is the definite source. That should work. > it's possible the bad jar got in there through the java repository Actually that's most likely the reason why > (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? What would you like to ask? Once the new release is out the door I could update the jar and put the new one up. How does that sound? > but +1 to actively pushing a fix out however it's done... Yes, let's fix it cheers -- Torsten
signature.asc
Description: OpenPGP digital signature
