Yeah, can't pull it back. Just need to push a new version.

On 05/27/2015 05:57 PM, Phil Steitz wrote:
Somehow the 2.4 binary release jar that I just pushed to the mirrors
and maven central appears to be corrupted.  I don't know why / how
this happened but I get the following error when I build dbcp with
the new jar:

net/sourceforge/cobertura/coveragedata/TouchCollector
java.lang.NoClassDefFoundError:
net/sourceforge/cobertura/coveragedata/TouchCollector
     at
org.apache.commons.pool2.impl.AbandonedConfig.__cobertura_init(AbandonedConfig.java)

There is also a coberta.properties file in the manifest.  I have no
idea how it happened, but somehow maven seems to have created the
release jar from the coberta-instrumented classes or something.

The hashes and sigs on the jar are all good.

I would appreciate some help figuring out what is going on here and
also pushing out a quick fix release, as I suspect there is no way
we can pull back what I pushed out about 10 hours ago.

Sorry to have not caught this prior to pushing the binaries out and
thanks in advance for any help anyone can provide.

Phil


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to