Databases
StackOverflow2013
Postsdbo
POProblem upgrading to GWT 2.3.0
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProblem upgrading to GWT 2.3.0
    primarykey
    data
    text
    <p>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:</p> <pre><code>[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 </code></pre> <p>&lt; Huge stack-trace removed ></p> <pre><code>[INFO] [ERROR] Failure while parsing XML [INFO] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) </code></pre> <p>&lt; Huge stack-trace removed ></p> <pre><code>[INFO] [ERROR] Unexpected error while processing XML [INFO] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) </code></pre> <p>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.</p> <p>Does anyone know what might be going on here? Any idea what logging "strategy" Google is using here :).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGunnar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProblem upgrading to GWT 2.3.0
      1. USReddy
      1. VTFavorite
    2. VO
      singulars
      1. POProblem upgrading to GWT 2.3.0
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POProblem upgrading to GWT 2.3.0
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm also having this problem while updating from 2.3.0 to 2.4.0, and I verified that both gwt-dev, gwt-user and gwt-servlet are all on the same version. Any one has any clues?
      singulars
      1. POProblem upgrading to GWT 2.3.0
      1. USuser469243
    2. COI also had the same problem moving from 2.3 to 2.4 and the answser from @twelve17 works here too, i.e. all I had to do was modify my pom to ensure that the version of gwt-maven-plugin was at least as new as that of gwt-servlet etc., i.e. I had been using a 2.3 version of gwt-maven-plugin and updated it to 2.4.0.
      singulars
      1. POProblem upgrading to GWT 2.3.0
      1. USGeorge Hawkins
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload