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

Bug 185118

Summary:	Provide API to invoke the JDT compiler in Eclipse and standalone mode
Product:	[Eclipse Project] JDT	Reporter:	Marius Slavescu <slavescu>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	david_audel
Version:	3.3
Target Milestone:	3.4 M6
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Marius Slavescu

2007-05-02 10:21:46 EDT

Currently I'm using boolean org.eclipse.jdt.internal.compiler.batch.Main.compile(String commandLine, PrintWriter outWriter, PrintWriter errWriter). 
Would be a plus if better error reporting (instead of the writers) can be provided (even for this kind of invocation).

I would like to get an API supported mechanism to invoke the JDT compiler in Eclipse  and standalone mode.

Would be great if I can do the compilation in memory and also avoid using a Java project or workspace (especially for standalone mode), something similar with what http://jakarta.apache.org/commons/jci/ provides.

I can provide more details when required.

Comment 1 Marius Slavescu

2007-05-02 10:23:26 EDT

I need this kind of support for JRE 1.4 and up, I understand JCI capability is available in JRE 1.6 through JSR 199.

Comment 2 Jerome Lanneluc

2008-08-22 11:08:11 EDT


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

Comment 3 David Audel

2008-09-16 07:41:31 EDT

Verified for 3.5M2

Comment 4 Paul Slauenwhite

2009-06-30 09:35:45 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

Comment 5 Paul Slauenwhite

2009-06-30 10:00:23 EDT

This enhancement/defect was mistaken closed as part of the TPTP 4.6 Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes) since the originator of this enhancement/defect has an inactive Bugzilla account.  If this enhancement/defect is still unresolved and reproducible, please re-open.