commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz SÅ‚owikowski <gslowikow...@gmail.com>
Subject Re: [pool] apparently bad jar released ... ugh. help!
Date Thu, 28 May 2015 11:47:07 GMT
Hi

I think, I know the reason, I've had similar problem.

This commit
http://svn.apache.org/viewvc/commons/proper/pool/trunk/pom.xml?view=diff&r1=1680128&r2=1680129&pathrev=1680129
upgraded cobertura plugin's version to 2.7.

There is new, VERY "DANGEROUS" reporting mojo in 2.7 -
"cobertura-integration-test"
(http://mojo.codehaus.org/cobertura-maven-plugin/cobertura-integration-test-mojo.html)
During processing in foked lifecycle it overrides the project artifact
jar file with the instrumented version.

This mojo should be avoided if possible IMO, but Maven site plugin runs
all reporting mojos when generating site. You have to configure
reportsets adding only "cobertura" reportset.
See "Using different reports" section in
http://mojo.codehaus.org/cobertura-maven-plugin/usage.html

I see there is issue already reported -
http://jira.codehaus.org/browse/MCOBERTURA-203

Regards
Grzegorz Slowikowski

On 2015-05-27 23:57, 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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> .
> 

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


Mime
View raw message