Hans Dockter wrote:
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.
We would still have this problem if builds do their own writing to
stdout, or if they fork processes, or if they use these ant tasks (or
ones like them) directly.
To solve the problem, we could bridge stdout and stderr across to
logging, with default info level for stdout and error level for stderr.
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.
I agree. Junit 4 is very easy to invoke directly, and I'm pretty sure
test-ng is as well.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
