ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8745] New: - log compile errors so that they can be picked up by the BuildListeners
Date Thu, 02 May 2002 16:15:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8745>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8745

log compile errors so that they can be picked up by the BuildListeners

           Summary: log compile errors so that they can be picked up by the
                    BuildListeners
           Product: Ant
           Version: 1.4.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: dsmith@hywy.com


I use Ant programmatically and I made my own BuildListener to capture the Ant 
events, however compilation errors are not passed back as events.  Previously, 
I made my own PrintStream and set the System.err to it so that I could
catch the compile errors.

When I moved to Java 1.4 and Ant 1.4.1 in order to compile 1.4 specific code, 
this stopped working.  If I switch back the compiler, it works again, so I know 
it isn't something that Ant is doing. 
 
I noticed that in the old compiler the Main() javac costructor can take an 
OutputStream (PrintStream) as a parameter.  If the user could define a print 
stream to use, that would be good.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message