Most reviewers evaluate the release candidate based on the sources.  Other than 
the bugged plugin reference in the pom, there is nothing wrong with the 
sources.  What was defective was the compiled jar.  It was correctly hashed and 
signed, but due to nasty plugin bug it ended up containing instrumented classes.

This is my responsibility as rm. in the future I will separately test compiled 
jars and I recommend that other reviewers do the same as we apparently cannot 
count on correct functioning of packaging tools.



> On May 28, 2015, at 6:15 PM, Dan Tran <dant...@gmail.com> wrote:
> 
> Just curious, how did this pass the staging test during the vote?
> 
> Thanks
> 
> -D
> 
>> On Thu, May 28, 2015 at 4:10 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
>> 
>> I burned the time I had last night trying to figure out what was going on
>> before I saw Grygorz' explanation and I have been out of pocket today.
>> Will not be able to get to this until toMorrow.
>> 
>> 
>> 
>>>> On May 28, 2015, at 3:27 PM, Gary Gregory <garydgreg...@gmail.com>
>>> wrote:
>>> 
>>> Since the bad jars are percolating through mirrors or have already done
>> so,
>>> I do not see another choice but releasing a 2.4.1.
>>> 
>>> Gary
>>> 
>>> On Thu, May 28, 2015 at 11:13 AM, James Carman <
>> ja...@carmanconsulting.com>
>>> wrote:
>>> 
>>>>> On Thu, May 28, 2015 at 1:56 PM sebb <seb...@gmail.com> wrote:
>>>>> 
>>>>> 
>>>>> Still needs a vote IMO.
>>>> Yes, if the binaries we voted on were actually corrupt and it wasn't
>>>> something that got corrupt during transfer, then we need to re-build the
>>>> binaries and re-vote on them.
>>> 
>>> 
>>> 
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>> 
>> ---------------------------------------------------------------------
>> 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