The dependency is on jdt.core - primarily to support the java:class,
java:package and java:resource tags.
It is my hope to refactor JET into smaller pieces so that it can run on
things like RCP, but at this point, that refactoring is incomplete (and will
not be complete in the Europa timeframe).
If you would like to explore using JET in RCP, I am very willing to help
you, and then use your experiences to drive refactoring.
Let me know,
JET Lead developer
"Henrik" <firstname.lastname@example.org> wrote in message
> We are developing a RCP application with a EMF editor. This EMF data will
> then be converted to C source code. I would like to some kind of code
> generator for this, e.g. JET.
> I read that JET2 depends on JDT. Is it the whole JDT or only some parts of
> As I am developing a RCP application I don't want to let the user see JDT
> menu actions.