Without any cited cases I am prepared to believe that someone is
programatically processing default log output in such a way that it
would break if it found one of..
compile @ 1 minute 12 seconds:
compile (1 minute 12 seconds):
compile:
(at 1 minute 12 seconds)
.. and that it would be too much for that team to fix their
application to accommodate the new info.
Perhaps an ant.exe command line switch could do it ( -timedTargets )
or an environmental variable ( -DtimedTargets=true )
Bugzilla bug 27771 is in the same realm too - http://
issues.apache.org/bugzilla/show_bug.cgi?id=27771 and hints that an
additional temporal element to the Default Logger output would be
problematic.
- Paul
On Aug 14, 2006, at 4:58 AM, Jeffrey E Care wrote:
I wouldn't make the assumption that ALL automated log analyzers use
the XML format.
______________________________________________________________________
______________________
Jeffrey E. (Jeff) Care
[EMAIL PROTECTED]
IBM WebSphere Application Server Development
WAS Pyxis Lead Release Engineer
"Paul Hammant" <[EMAIL PROTECTED]> wrote on 08/11/2006 04:34:21 PM:
>
> Alexey,
>
> > This one works: dir ham.txt>output.log 2>&1
>
> ant [target] >output.log 2>&1
>
> .. works well.
>
> Tis up to you guys to change the DefaultLogger or not. It sure looks
> nice when you run it and there's no harm as electronic processors of
> Ant output (like CruiseControl) use the XML logger.
>
> - Paul
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
