CODEWITHSUNDEEP
gwt
Gunnar
Gunnar

Reputation: 41

Problem upgrading to GWT 2.3.0

I'm totally flummoxed by a GWT problem, and have no clue how to interpret the GWT log or how to troubleshoot the problem. I'm working on a fairly trivial template project. I upgraded to GWT 2.3.0 and am now running into the following issue when compiling the module using the maven-gwt-plugin:

[INFO] --- gwt-maven-plugin:2.3.0:compile (default) @ gaewebtemplate ---
[INFO] auto discovered modules [stuff.gaegwttemplate.Main, stuff.gaegwttemplate.security.SecurityRequest]
[INFO] Loading inherited module 'com.google.gwt.activity.Activity'
[INFO]    Loading inherited module 'com.google.gwt.place.Place'
[INFO]       Loading inherited module 'com.google.gwt.user.User'
[INFO]          Loading inherited module 'com.google.gwt.animation.Animation'
[INFO]             Loading inherited module 'com.google.gwt.core.Core'
[INFO]                Loading inherited module 'com.google.gwt.core.CrossSiteIframeLinker'
[INFO]                   [ERROR] Unable to load class 'com.google.gwt.core.linker.DirectInstallLinker'
[INFO] java.lang.ClassNotFoundException: com.google.gwt.core.linker.DirectInstallLinker

< Huge stack-trace removed >

[INFO]                   [ERROR] Failure while parsing XML
[INFO] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)

< Huge stack-trace removed >

[INFO]                   [ERROR] Unexpected error while processing XML
[INFO] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)

The two stack traces and cryptic error messages above is then repeated creating page after page of (as far as I can tell) completely useless log information.

Does anyone know what might be going on here? Any idea what logging "strategy" Google is using here :).

Upvotes: 4

Views: 6597

Answers (3)

Chrissy
Chrissy

Reputation: 155

I got the same error when upgrading from gwt 2.3 to gwt 2.4. I was being silly and updated the version on the gwt-user dependency but not on the gwt-dev dependency. So, check that you aren't also being silly.

Upvotes: 0

twelve17
twelve17

Reputation: 718

Gunnar,

I ran into a similar issue. If you are trying to use a GWT SDK newer than the maven plugin, you have to also point the maven plugin to that SDK, like this:

http://mojo.codehaus.org/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html

Otherwise, I believe the maven plugin will still use the GWT version that matches it (if you were to delete your GWT jars from your maven repo, you could confirm this by seeing it downloading the older version.)

Upvotes: 10

Colin Alworth
Colin Alworth

Reputation: 18346

The DirectInstallLinker class doesn't appear to be present in GWT 2.3, but I do see it in trunk - are you sure you are using 2.3.0? To get this error, it seems likely that you have at least one copy of something newer than 2.3.0 on your classpath.

GWT 2.3.0 was released on May 2, while the DirectInstallLinker doesn't appear to have been added to source until May 6.

The GWT compiler is using the TreeLogger class, built in to GWT as a way for the compiler and generators to nest debug/error/info messages.

Upvotes: 1

Related Questions