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 instr
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 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 abl
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 wrote:
>
> Since the bad jars are percolating throug
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
wrote:
> On Thu, May 28, 2015 at 1:56 PM sebb wrote:
>
> >
> > Still needs a vote IMO.
> >
> >
> Yes, if the binari
On Thu, May 28, 2015 at 1:56 PM sebb 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.
>> >>> On Wed, May 27, 2015 at 9:48 PM Gary Gregory
>> wrote:
>> >>>
>> >>> I think we need a vote no matter what for a new release. What we can
>> do is
>> >>> make the vote 24 hours instead of 72.
>> >>> Gary
>&g
On 5/28/15 6:47 AM, Grzegorz Słowikowski wrote:
> 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
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-integr
>
> >>> On Wed, May 27, 2015 at 9:48 PM Gary Gregory
> wrote:
> >>>
> >>> I think we need a vote no matter what for a new release. What we can
> do is
> >>> make the vote 24 hours instead of 72.
> >>> Gary
> >>>
>
the 2.4
>>> release sources are consistently clean would be appreciated.
>>>
>>> In any case, I am fine running another vote once I have 2.4.1 artifacts.
>>>
>>> Phil
>>>
>>>
>>>>> On Wed, May 27, 2015 at 9:48 PM Gary
>>
>> Phil
>>
>>
>>>> On Wed, May 27, 2015 at 9:48 PM Gary Gregory
>>>> wrote:
>>>>
>>>> I think we need a vote no matter what for a new release. What we can do is
>>>> make the vote 24 hours instead of 72.
>&
>> Original message --------
>>> From: Phil Steitz
>>> Date: 05/27/2015 17:54 (GMT-08:00)
>>> To: Commons Developers List
>>> Subject: Re: [pool] apparently bad jar released ... ugh. help!
>>>
>>> OK, having calmed down a bit, I have a pl
; make the vote 24 hours instead of 72.
>> Gary
>>
>> Original message
>> From: Phil Steitz
>> Date: 05/27/2015 17:54 (GMT-08:00)
>> To: Commons Developers List
>> Subject: Re: [pool] apparently bad jar released ... ugh. help!
>&
From: Phil Steitz
> Date: 05/27/2015 17:54 (GMT-08:00)
> To: Commons Developers List
> Subject: Re: [pool] apparently bad jar released ... ugh. help!
>
> OK, having calmed down a bit, I have a plan. Feedback, objections,
> general grumpiness welcome.
>
> 0. Open JIRA a
I think we need a vote no matter what for a new release. What we can do is make
the vote 24 hours instead of 72.
Gary
Original message
From: Phil Steitz
Date: 05/27/2015 17:54 (GMT-08:00)
To: Commons Developers List
Subject: Re: [pool] apparently bad jar released
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 d
OK, having calmed down a bit, I have a plan. Feedback, objections,
general grumpiness welcome.
0. Open JIRA against 2.4
1. Revert web site update
2. Drop 2.4 artifacts from release area
3. Copy 2.4 release tag to make 2.4.1 release tag
4. Roll good artifacts from 2.4.1 tag. If these do not test o
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.NoClassDefFoundErr
18 matches
Mail list logo
