Does this mean that I'll finally be
able to specify enable-assertions for my unit tests without having to remind
every developer who downloads my code to set MAVEN_OPTS=-ea
I hope so.
Kind regards,
Dave Sag
Jason van Zyl <[EMAIL PROTECTED]> wrote on 28-11-2005
03:02:25:
> Hi,
>
> Sure
Alright, I think there are only two issues we can't get along without
for this release...testng and the issue having to do with the
bootclasspath (which I'm currently on, but don't think it should hold
things up).
For the remaining two issues (not bootclasspath or testng), these are
related t
+1 from me.
I think applying stuff with patches and small issues is important, but
don't want to hold this up either. It should have been in the first
release :)
Thanks for sorting it out Jason!
Cheers,
Brett
Jason van Zyl wrote:
> John Casey (Yahoo!) wrote:
>> It looks like the maven-surefire-
John Casey (Yahoo!) wrote:
It looks like the maven-surefire-plugin has 5 open issues currently. One
of them is the forking issue, another is related (but requires its own
fix), and still another is outside the scope of the current release, IMO
(testng support). Can we get those remaining 4 issu
+1, the test forking worths a release
fabrizio
On 11/28/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Surefire will now fork tests and I've updated the surefire plugin
> accordingly so I think it's time for a release.
>
> +1
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http:
SUREFIRE-19 has patches as well, but I am willing to bet that only impacts
screwed up testing harnesses like the one I am working on atm :)
jesse
On 11/28/05, John Casey (Yahoo!) <[EMAIL PROTECTED]> wrote:
>
> actually, that surefire issue is SUREFIRE-16
>
> John Casey (Yahoo!) wrote:
> > It look
actually, that surefire issue is SUREFIRE-16
John Casey (Yahoo!) wrote:
It looks like the maven-surefire-plugin has 5 open issues currently. One
of them is the forking issue, another is related (but requires its own
fix), and still another is outside the scope of the current release, IMO
(test
It looks like the maven-surefire-plugin has 5 open issues currently. One
of them is the forking issue, another is related (but requires its own
fix), and still another is outside the scope of the current release, IMO
(testng support). Can we get those remaining 4 issues figured out before
relea
+1
On 11/28/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Lukas
>
>
> Jason van Zyl wrote:
> > Hi,
> >
> > Surefire will now fork tests and I've updated the surefire plugin
> > accordingly so I think it's time for a release.
> >
> > +1
> >
>
>
+1
Lukas
Jason van Zyl wrote:
Hi,
Surefire will now fork tests and I've updated the surefire plugin
accordingly so I think it's time for a release.
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
+1
Vincent
2005/11/27, Jason van Zyl <[EMAIL PROTECTED]>:
> Hi,
>
> Surefire will now fork tests and I've updated the surefire plugin
> accordingly so I think it's time for a release.
>
> +1
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> In short, man creates
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: lundi 28 novembre 2005 03:02
> To: Maven Developers List
> Subject: [vote] surefire/maven-surefire-plugin release
>
> Hi,
>
> Surefire will now fork tests and I've updated the
+1
Emmanuel
Jason van Zyl a écrit :
Hi,
Surefire will now fork tests and I've updated the surefire plugin
accordingly so I think it's time for a release.
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Hi,
Surefire will now fork tests and I've updated the surefire plugin
accordingly so I think it's time for a release.
+1
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work a
14 matches
Mail list logo