Hi,
some Ant tasks don't use the Ant logging system for some of there
messages but use System.out.println instead. For example the javac
tasks does this with warnings from the compiler. The launch4j tasks
does this as well. There is not much we can do about this as long as
we use those tasks. Sooner or later I think we should have native
implementations of our core tasks. Not just because of logging. It
would also increase our flexibility.
Another problem is the Ant Junit tasks. It does not offer something
like a test summary. Therefore in our high level log the user can't
find out which tests have failed. They have to look into the test
reports. But also with INFO logging it is very inconvenient to find
the test which has failed. When implementing testng integration I
would like to refactor our test task not to rely on Ant Junit any
longer but have there own test runners instead. What I also dislike
about the JUnit Ant task is that it tries to execute Abstract test
cases. You have to explicitly exclude them.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
