Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 137389

Summary:	JDT Batch compiler should generate Problems like the internal compiler does
Product:	[Eclipse Project] JDT	Reporter:	Sean Adams <seadams>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Sean Adams

2006-04-18 18:34:48 EDT

When calling the batch compiler within Eclipse -- say via an Ant builder -- the warnings and errors should show up in the Problems view as well as on the console.

Basically this is a usability issue -- it is *much* easier to fix problems by double-clicking something in the Problems view than to hunt through the console to dins thing to double-click on.

If someone wants to point me in the right direction, I'd be happy to work on this myself.

Comment 1 Olivier Thomann

2006-04-18 20:56:44 EDT

Also from the N&N from M6:

Java problem markers from a "javac" build
	

Running an Ant build that contains a "javac" declaration can produce JDT problem markers for the code that is compiled. The marker generation is controlled by an Ant UI preference: Window > Preferences > Ant > Create problem markers from "javac" results. As well, the "javac" declaration needs to set the "listfiles" attribute to "true" and an Eclipse console must be allocated for the build output.

*** This bug has been marked as a duplicate of 133184 ***