Re: How to post priority="warn" messages from a build tool?

Douglas Pearson <[email protected]>
Newsgroups gmane.comp.java.cruise-control.user
Message-ID <[email protected]>
In case anyone else encounters this problem it appears that ant 1.7.x
generates "warn" level messages in conjunction with cruise control and ant
1.8.x generates "info" level.

So for now we've "solved" this by rolling ant back to 1.7.

Doug

On Tue, Apr 5, 2011 at 8:23 PM, Douglas Pearson <[email protected]> wrote:

> We have a build tool (it runs in Java via an ant task).  When it fails, it
> dumps output to stderr and returns an error code of 1.
>
> This is corrected detected by cruise control as a failed build.  However
> the generated output appears as lines like this in the logs:
>
>        <target name="run-items" time="4 minutes 6 seconds">
>           <task location="/var/tomcat/svn/Main/Source/Java/build.xml:635: "
> name="java" time="4 minutes 6 seconds">
>             <message priority="info"><![CDATA[** Error Clothing without an
> item.xml file with item 2032741]]></message>
>             ...
>
> Because this is only "info" level priority message, it's not included in
> the email that's generated and sent out.
>
> Is there a way to have the tool generate output which will be classified as
> priority="warn" or priority="error", so it'll appear in the email?
>
> If it's not possible, do we need to modify the XSL so it sends out all
> "info" lines or is there some option to do that w/o us hacking XSL?
>
> Doug
>
>

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.