sorry every one, i did you use it in production, but not this particular
usecase where my
group begin to write JNI unittest starting 2.0.3 ;-) Next time, I will be
more carefull with
what I announce ;-)
-D
On 3/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> > I would prefer (b). 2.0.3 had
> I would prefer (b). 2.0.3 had a release candidate for weeks and no one
> reported this bug.
Funnily enough, the first to find it was Dan, who said that he was using
the release candidate in production :) Obviously not the last one...
> Short circuiting the process is unjustified IMO.
> 2.0.4
orter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 30, 2006 8:15 AM
To: Maven Developers List
Subject: URGENT: release Maven 2.0.4
Hi,
I'd like to determine what the best course of action is, so figured we
should take a straw poll.
Maven 2.0.3 contained a major regression, that caused certai
ECTED]
Sent: Thursday, March 30, 2006 8:15 AM
To: Maven Developers List
Subject: URGENT: release Maven 2.0.4
Hi,
I'd like to determine what the best course of action is, so figured we
should take a straw poll.
Maven 2.0.3 contained a major regression, that caused certain paths to
inco
ently
preventing any further release...
Thanks
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 30 mars 2006 16:15
> To: Maven Developers List
> Subject: URGENT: release Maven 2.0.4
>
> Hi,
>
> I'd like to determine
Hi,
I'd like to determine what the best course of action is, so figured we
should take a straw poll.
Maven 2.0.3 contained a major regression, that caused certain paths to
incorrectly be interpolated in the POM (MNG-2183).
I have fixed it, and also a regression since 2.0 (MNG-2054). I have
updat
