Even easier, if we create a property for maven.junit.toFile which defaults
to true, and put that on the current plain formatter, it should work.
Berin,
do u want to give this a go?
1) Create a property in ~/build.properties:
maven.junit.toFile=false
2) Edit ${maven.home}/build-test.xml
a) remove the second plain formatter we added.
b) on the type="plain" formatter, add the usefile="${maven.junit.toFile}"
attribute
3) Run tests....
I think this will work.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
"Glenn A. McAllister" <[EMAIL PROTECTED]>
05/12/02 02:40 AM
Please respond to "Turbine Maven Users List"
To: Turbine Maven Users List <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
cc:
Subject: RE: Turbine swallows test information
On Sat, 11 May 2002, Berin Loritsch wrote:
> > From: Stéphane MOR [mailto:[EMAIL PROTECTED]]
> > Maybe something like maven.test.verbose = true | false ...
> >
>
> That would work. But this is a case where it may actually
> be easier to decide on one way or another to do things.
> I don't believe the <junit><formatter/></junit> entry supports
> an "unless" attribute.
Well, we can create a separate targets, on with if="maven.test.verbose"
and the other with unless="maven.test.verbose". The only problem there of
course is the fact that the targets will be 99% the same...
Glenn McAllister
SOMA Networks, Inc.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
