2012/1/5 Konstantin Kolinko <knst.koli...@gmail.com>:
> 2011/12/30 Brian Burch <br...@pingtoo.com>:
>>>
>>> Formatter is configurable since 7.0.24.
>>
>>
>> Silly me! A ${test.formatter} property is defined immediately after
>> ${test.name}!The test.formatter configures logging library (or specifically org.apache.juli.logging.DirectJDKLog) when no logging.properties configuration is available. That is a different beast. I was referring to "junit.formatter.type" property. >> However, the runtests macro assumes I want usefile="true", but >> that prevents netbeans from intercepting the results. > > You can convert usefile flag into a property as well, > <property name="junit.formatter.usefile" value="true"/> > I added the above "junit.formatter.usefile" property in trunk and 7.0.x, so you may experiment with it. (Our own advantage from this is that we maybe can configure buildbot to use this property - If it cannot be configured to publish proper JUnit reports). >> >> I will think about whether I really want both formatters active on the same >> netbeans test run (as in my current version). If not, I need to work out how >> to inject a value without the user having to change it in build.properties, >> where it would affect non-netbeans test runs. >> > > You may look here for an inspiration: > https://issues.apache.org/bugzilla/show_bug.cgi?id=52237 > Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
