yes, it is :-( I got unresolved imports without it. I cannot say why exactly but I can find it if required.
Curiously, the dependency of JDT from Jetty Orbit, which is the most close to the JDT jar available on GWT-Tools, include the contents of jdtCompilerAdapter.jar, but with the Jetty artifact there ware other missing imports and I had to move to the approach suggested by Thomas and deploy them to the Maven repo (even if I did it with a partially automated process that adds them from the GWT tools folder during the maven build). I've made progresses but I'm still far from my goal, thank you again for now. 2013/10/21 Roberto Lublinerman <[email protected]> > On Sun, Oct 20, 2013 at 3:21 PM, Thomas Broyer <[email protected]> wrote: > > See $GWT_TOOLS/lib/eclipse/README.jdt-upgrade (last paragraph), and >> comments in https://gwt-review.googlesource.com/#/c/2361/1/dev/build.xml (if >> you understand them; reading them now, I don't ;-) ) >> > > In retrospective I am not sure if extracting jdtCompilerAdapter.jar from > JDT is really needed. > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
