Bug 97444 - Possibility to use the JDT compiler API outside of a running workbench
Summary: Possibility to use the JDT compiler API outside of a running workbench
Status: RESOLVED DUPLICATE of bug 87852
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-31 08:41 EDT by Georg Lenz CLA
Modified: 2006-03-31 13:34 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Lenz CLA 2005-05-31 08:41:31 EDT
Possibility to use the JDT compiler via official API outside of a running workbench


Remarks:
If we had ASTParser out side of a running workbench our problems would be
solved, but it lives inside the context of I(Java)Project. Therefore we use
“Compiler” it is standalone but internal and undocumented. 
If the things done in
http://www-128.ibm.com/developerworks/opensource/library/os-ast/
 could be considered “official documentation” our problems would be solved.

Summary of current problems: 

We are using the compiler for AST-based static code analysis outside of a
running workbench environment, e.g. in a build environment. We are forced to use
the internal org.eclipse.jdt.internal.compiler.ast.* classes instead of the
official org.eclipse.jdt.core.dom.* API.
Comment 1 Philipe Mulet CLA 2006-03-30 07:07:38 EST
The DOM AST can now be used again outside Eclipse.
Comment 2 Olivier Thomann CLA 2006-03-31 13:34:26 EST

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