You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Peter Lynch <pe...@mindspring.com> on 2003/02/02 07:00:12 UTC

Re: cvs commit: jakarta-turbine-maven/src/test/touchstone-buildmaven.xml

----- Original Message -----
From: "Jason van Zyl" <ja...@zenplex.com>
To: "Turbine Maven Developers List" <tu...@jakarta.apache.org>
Sent: Saturday, February 01, 2003 9:47 PM
Subject: Re: cvs commit:
jakarta-turbine-maven/src/test/touchstone-buildmaven.xml


> On Sat, 2003-02-01 at 23:58, Ben Walding wrote:
> > I've commented out the failing test. Maven-242 has been raised to
> > reenable it when appropriate
> >
> > While I appreciate what you did, a non functional HEAD makes life
> > extremely difficult for those of us who do clean builds to check that
> > our changes haven't hosed something else.  It also contributes to a raft
> > of discussion on the mailing lists and IRC as people cumulatively waste
> > hours trying to solve it for themselves.
> >
> > I think this falls into the realm of test categories - fast, slow,
> > broken etc.  If I could disable the known broken tests that would suit
> > my purposes.  And conversely, any known broken test that worked should
> > count as a failure! (so that it can be moved to working tests)
>
> It's certainly good to put failing tests into the touchstone build, just
> leave it out of the 'touchstone-tests' goal until the problem is solved.


Ahh ok, will do.

-Peter

>
> > Cheers,
> >
> > Ben

<snip />