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
Mike Perham wrote:
It's actually MNG-2186.
I would prefer (b). 2.0.3 had a release candidate for weeks and no one
reported this bug. Short circuiting the process is unjustified IMO.
2.0.4 could be released on Sunday with the normal process.
-Original Message-
From: Brett Porter [mailt
It's actually MNG-2186.
I would prefer (b). 2.0.3 had a release candidate for weeks and no one
reported this bug. Short circuiting the process is unjustified IMO.
2.0.4 could be released on Sunday with the normal process.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
You might also be interested by http://jira.codehaus.org/browse/MNG-2184. It
would be good to confirm if this is indeed a bug and if so possibly make it
part of 2.0.4. Not sure of the importance compared to other things; I just
know that it's a major issue for the clover plugin that is currently
pr
