Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST

Great that most dependencies are referenced now.

You are right, the extra JDT library should not even be on the GWT classpath.  

We use the gwt-gradle-plugin to compile GWT projects with gradle, maybe our configuration is not correct there.

On Tuesday, August 2, 2016 at 6:03:37 PM UTC+2, Thomas Broyer wrote:

On Tuesday, August 2, 2016 at 5:50:22 PM UTC+2, Uwe Maurer wrote:

Thanks for the hint. Yes, the problem was that GWT SDK duplicates these JDT classes instead of depending on the corresponding library.

JDT is the only dependency that's still bundled into GWT, and this is the case because a) it uses a patched JDT (for a memory issue) and b) it uses internal APIs that are "normally" hidden into a JAR (yes, a JAR inside a JAR) and aren't available in any artifact in any Maven repo (that I know of).

Note: GWT has always bundled its dependencies. It's only starting with 2.8.0-rc1 that dependencies are "referenced" instead; except for JDT.

BTW, what's the reason you have JDT and gwt-dev in the same classpath/scope/configuration? Are you using JDT in client-side code? (a GWT generator?) If not, Gradle is flexible enough so you can correctly segregate dependencies depending on their use.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.