I had some trouble with the current version 1.2 of the Google Web Toolkit Maven Plugin since it apparently does not support some of the 2.1.0 features. After google-ing for some minutes I found a repository for both the GWT 2.1.0.M2 SDK and a special (ahem) 1.3.1.google version for the Maven plugin:

<dependency>
  <groupId>com.google.gwt</groupId>
  <artifactId>gwt-servlet</artifactId>
  <version>2.1.0.M2</version>
  <scope>runtime</scope>
</dependency>
<dependency>
  <groupId>com.google.gwt</groupId>
  <artifactId>gwt-user</artifactId>
  <version>2.1.0.M2</version>
  <scope>provided</scope>
</dependency>
 
<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>gwt-maven-plugin</artifactId>
  <version>1.3.1.google</version>
</plugin>
 
<repository>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
  <id>gwt-dev-release</id>
  <url>http://google-web-toolkit.googlecode.com/svn/2.1.0.M2/gwt/maven/</url>
</repository>
 
<pluginRepository>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
  <id>gwt-dev-release</id>
  <url>http://google-web-toolkit.googlecode.com/svn/2.1.0.M2/gwt/maven/</url>
</pluginRepository>

1. cd .metadata/.plugins
2. mv org.eclipse.core.resources org.eclipse.core.resources.bak
3. Start eclipse. (It should show an error message or an empty workspace because no project is found.)
4. Close all open editors tabs.
5. Exit eclipse.
6. rm -rf org.eclipse.core.resources (Delete the newly created directory.)
7. mv org.eclipse.core.resources.bak/ org.eclipse.core.resources (Restore the original directory.)
8. Start eclipse and start working. :-)

 * NOTE: This class is still very new, and its interface
 * may change without warning. Use at your own risk.

and

* TODO(jgw):
 * - RTL Support.
 * - implement insert().
 * - Come up with a decent way to specify splitter style and size.

OK, I use it at my own risk and use a not so decent way to change the style of the splitters:

interface Binder extends UiBinder <SplitLayoutPanel, MyView> { }
private static Binder binder = GWT.create(Binder.class);
...
public MyView () {
  initWidget (binder.createAndBindUi (this));
}
...
public void setVDraggerHeight (String height)
{
  SplitLayoutPanel p = (SplitLayoutPanel) this.getWidget ();
  int widgetCount = p.getWidgetCount ();
  for (int i = 0; i < widgetCount; i++) {
    Widget w = p.getWidget (i);
    if (w.getStyleName ().equals ("gwt-SplitLayoutPanel-VDragger")) {
      w.setHeight (height);
    }
  }
}

→ Issue 4620: Hardcoded styling in SplitLayoutPanel

.gwt-TabLayoutPanelTab { float: left; }

to your CSS stylesheet.

→ TabLayoutPanel not working on IE8
→ Issue 4447: TabLayoutPanel tabs don’t line up properly on IE

In GWT development mode I had no problems signing in with my Google account. When running the application on Tomcat I got the following error: “Local signature verification failed” from the OpenID4Java ConsumerManager although I received a positive auth response and Google delivers my name and email address of my Google account.

The problem was a special character, a german umlaut, in my name which was not decoded properly with the correct character encoding. Because of this wrong URL encoding the calculated signature in the OpenID4Java Association was different from the original signature.

Adding the attribute URIEncoding=”UTF-8″ to the connector
element in Tomcat’s server.xml explicitly directs Tomcat to use UTF-8 character encoding instead of its default (ISO-8859-1) and fixed the problem.

→ Tomcat and UTF 8 encoding
→ Apache Tomcat Configuration Reference

<meta http-equiv="X-UA-Compatible" content="IE=7"/>

If you know the reason for this behavior please leave a comment.

apt-get remove libclamav3 clamav and every other dependency with apt-get autoremove and download and install all "*0.95.3*hardy2*.deb" packages from http://archive.ubuntu.com/ubuntu/pool/universe/c/clamav/ with dpkg -i libclamav*; dpkg -i install clamav*.

Have a nice weekend.

#!/bin/sh
export GDK_NATIVE_WINDOWS=true
YOUR_COMMAND_TO_START_ECLIPSE

See also:
→ Bug 291257 – [Widgets] Buttons functionality problem with GTK+ 2.18
→ Migrating to client-side windows