On Sun, 2005-10-30 at 09:20 +0100, Kenney Westerhof wrote:
> On Sun, 30 Oct 2005, Kenney Westerhof wrote:
>
> I'm obviously too late again :)
>
> Btw, why is it that when the vote was called the bootstrap still failed,
> but 23 hours later it succeeds?
I needed to make a release to fix the prob
On Sun, 30 Oct 2005, Kenney Westerhof wrote:
I'm obviously too late again :)
Btw, why is it that when the vote was called the bootstrap still failed,
but 23 hours later it succeeds? Shouldn't a call for a vote 'prove' a
problem has been fixed at that moment?
-- Kenney
> On Fri, 28 Oct 2005, Jas
On Fri, 28 Oct 2005, Jason van Zyl wrote:
+1, on one condition, that continuum can build m2 without failing :)
I don't see the bootstrap succeeding yet..
> Hi,
>
> I'd like to cut a release of the surefire plugin (along with a release
> of surefire itself) to fix a bug that caused the bootstrap
Not a problem. This emphasises for me the importance of getting JIRA for
plugins sorted out so we can all have the same expectations about what
will constitute the next release.
I understand Andy is working on his own time, but I think someone needs
to help him out to get it across the line. I
On 10/29/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> On Sat, 2005-10-29 at 17:00 +1000, Brett Porter wrote:
> > -0. I'd rather leave the "2.0" notation for one that includes forking
> > (which I thought we'd have for surefire 1.4 but it seems to have gone
> > silent). Let's push to finish that t
On Sat, 2005-10-29 at 17:00 +1000, Brett Porter wrote:
> -0. I'd rather leave the "2.0" notation for one that includes forking
> (which I thought we'd have for surefire 1.4 but it seems to have gone
> silent). Let's push to finish that this week.
It already went out a couple hours ago. I will ma
-0. I'd rather leave the "2.0" notation for one that includes forking
(which I thought we'd have for surefire 1.4 but it seems to have gone
silent). Let's push to finish that this week.
If it is 2.0-beta-X, +1.
- Brett
Jason van Zyl wrote:
Hi,
I'd like to cut a release of the surefire plugi
+1
Lukas
Jason van Zyl wrote:
Hi,
I'd like to cut a release of the surefire plugin (along with a release
of surefire itself) to fix a bug that caused the bootstrap to fail. The
bootstrap failing was caused by a bad POM which in turn revealed a bug
in surefire. I also applied a batch to prevent
+1
On 10/28/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> +1
>
> On 10/28/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> >
> > +1
> >
> > Emmanuel
> >
> > Jason van Zyl a écrit :
> > > Hi,
> > >
> > > I'd like to cut a release of the surefire plugin (along with a release
> > > of surefire it
+1
On 10/28/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Emmanuel
>
> Jason van Zyl a écrit :
> > Hi,
> >
> > I'd like to cut a release of the surefire plugin (along with a release
> > of surefire itself) to fix a bug that caused the bootstrap to fail. The
> > bootstrap failing was c
+1
Emmanuel
Jason van Zyl a écrit :
Hi,
I'd like to cut a release of the surefire plugin (along with a release
of surefire itself) to fix a bug that caused the bootstrap to fail. The
bootstrap failing was caused by a bad POM which in turn revealed a bug
in surefire. I also applied a batch to p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Jason van Zyl wrote:
| Hi,
|
| I'd like to cut a release of the surefire plugin (along with a release
| of surefire itself) to fix a bug that caused the bootstrap to fail. The
| bootstrap failing was caused by a bad POM which in turn revealed a bu
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: vendredi 28 octobre 2005 22:54
> To: Maven Developers List
> Subject: [vote] surefire plugin release
>
> Hi,
>
> I'd like to cut a release of the surefire plugin (along with a
Hi,
I'd like to cut a release of the surefire plugin (along with a release
of surefire itself) to fix a bug that caused the bootstrap to fail. The
bootstrap failing was caused by a bad POM which in turn revealed a bug
in surefire. I also applied a batch to prevent abstract test cases from
running.
14 matches
Mail list logo