We currently support debug information propagation (line numbering) and import statements in Oracle javac as well as through a preprocessor, but these cannot be used with Eclipse when running its native compiler. Specific support for the Eclipse compiler could be added dynamically in the same way that we support dynamic discovery of Javac classes. The Ant build script would have to be adjusted to account for that change and let people exclude plugins they do not want to compile.
Somebody on the mailing list has suggested borrowing ideas from Lombok ( http://projectlombok.org/ ) as they have very good Eclipse integration. This may involve playing with the internals of the JDT.
From nhat.min...@gmail.com on February 09, 2011 03:23:48
We currently support debug information propagation (line numbering) and import statements in Oracle javac as well as through a preprocessor, but these cannot be used with Eclipse when running its native compiler. Specific support for the Eclipse compiler could be added dynamically in the same way that we support dynamic discovery of Javac classes. The Ant build script would have to be adjusted to account for that change and let people exclude plugins they do not want to compile.
Somebody on the mailing list has suggested borrowing ideas from Lombok ( http://projectlombok.org/ ) as they have very good Eclipse integration. This may involve playing with the internals of the JDT.
Original issue: http://code.google.com/p/cofoja/issues/detail?id=12