This problem came up before in a different context (but I forgot to follow it up). The logging for stderr is set to priority error unless the task is run in a different jvm, in which case it is at level warning.
This is inconsistent and it would appear to be incorrect to set the priority to "error".
I think we should change the priority in this case to warning. This is of course not backward compatible.
Peter Falko Wiese wrote:
Hi,
we wrote our own xsl stylesheet for parsing ant log infos. With the message priorities (debug, info, warn, error) we want to decide whether our build run is complete, failed etc. We use ant version 1.5.4.
The output for the command 'ant -logger org.apache.tools.ant.XmlLogger -Dant.XmlLogger.stylesheet.uri=<stylesheet> -logfile <logfile> -verbose <targets> >/dev/null 2>&1' is the following:
...
<message priority="error"><![CDATA[ ^]]></message>
<message priority="error"><![CDATA[17 warnings]]></message>
</task>
</target>
</task> ...
Has anyone an idea, why the message priority is not 'warn'? Thanks a lot for help,
Falko Wiese.
------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
