Berin,
did the use of just the usefile attribute work for you? If so, I'll add the property and docs. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers "Berin Loritsch" To: "'Turbine Maven Users List'" <bloritsch@apa <[EMAIL PROTECTED]> che.org> cc: Subject: RE: Turbine swallows test information 05/12/02 02:13 AM Please respond to "Turbine Maven Users List" > From: Stéphane MOR [mailto:[EMAIL PROTECTED]] > > Berin Loritsch wrote: > > >Yep it did. The only thing is next time I update maven, > >I have to fix that again. > > > >Perhaps the build-test.xml needs to support this change. > >I am retisent to fall into the trap of everything being > >an option, but if some feel overwelmed by the output info > >of a TestCase, then perhaps it could be something where > >we respond by property. > > > 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. -- 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]>
