Bug 26606 - Ant errors not showing in console
Summary: Ant errors not showing in console
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows NT
: P2 normal (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Darin Swanson CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, ui
Depends on:
Blocks:
 
Reported: 2002-11-18 14:48 EST by Matthew Conway CLA
Modified: 2002-11-25 20:54 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Conway CLA 2002-11-18 14:48:09 EST 
Using the 2.1-M3 build, if I have an error in my ant file, and I do a "Run Ant"
on that buildfile, the error only shows up in .metadata/.log and not in the console

e.g.
<project name="foo" default="all">
	<target name="all">
		<echo xmessage="Howdy"/>
	</target>
</project>

The user shouldn't require intimate knowledge of eclipse in order to find out
errors that occurred while trying to run a build file.
Comment 1 Darin Swanson CLA 2002-11-19 00:48:36 EST 
A bug in the AntProcessBuildLogger. BuildEvents have a default priority 
of "verbose".
Reworked to correctly flag as error message BuildEvents that have an associated 
exception.

Create bug 26638 as we are logging too much to the log.
Comment 2 Darin Swanson CLA 2002-11-19 00:54:33 EST 
As well I changed the AntProcessBuildLogger to no longer use the priority codes 
of the LogConsoleDocument.  Instead it uses the priority codes of 
org.apache.tools.ant.Project.

Please verify changes to AntProcessBuildLogger and NullBuildLogger (Darin W).
Comment 3 Matthew Conway CLA 2002-11-19 10:55:34 EST 
Verified
Comment 4 Darin Wright CLA 2002-11-19 14:12:07 EST 
Verified the error shows in the console - so we should no longer log the error 
to the .log file.
Comment 5 Darin Swanson CLA 2002-11-25 20:54:16 EST 
Extra logging handled by bug 26638