On Thu, Jul 22, 2010 at 11:57 AM, James Laska <[email protected]> wrote:
> Based on the above failures, I could use some guidance/clarification. > > 1) I see use of org.eclipse.jdt.internal.*, my understanding is that > these internal objects are not guaranteed to be available in future > versions of jdt. I gather there are missing API's which required > using the internal objects? Are there any plans to remove use of > internal jdt objects? > No, as we have to have access at a lower level, since GWT doesn't primarily use the bytecode of the compilation but rather the symbol tables and AST. > 2) Fedora currently ships jdt-3.6. Are there plans to update gwt to > support jdt-3.6? > We have generally upgraded JDT only when we had to for some other reason. Aside from the internal APIs issue above (and the fact that they change), the JDT integration has been the source of a number of subtle bugs and it requires significant engineering effort to safely upgrade. I suggest one of the following: - package a gwt-jdt that has the specific version used by GWT and make that a dependency - incorporate this version of JDT into the GWT package, perhaps renaming the classes using jarjar/etc to avoid conflicts - have GWT depend on the specific version of JDT, though that might result in people being unable to use other packages that need later versions of JDT -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
