Friday, October 25, 2013

BUG? GWT modules inherit: filepath vs classpath

Hi everybody,

I have the following situation

There are 3 projects. Let's call them application_project,
library_project, datatype_project.

The application_project depends on the other two. However only the
datatype_project project is supposed to be compiled to javascript. So
the there is a .gwt.xml inside the datatype_project.

Now the problem is that library_project and datatype_project have the
same package structure. So the unified tree looks like{dir1/,dir2/ from library_project, datatype/ from

The gwt.xml inside datatype_project is located at and has
!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit
<inherits name="" />
<source path="lib"></source>

The problem is that the gwt compiler is trying to compile staff from the
library_project just because the classpath is matching
( I thought that the <source path=> directive was about
files and directories and not classpath. Finally in
there is the following statement.

Source Path

Modules can specify which subpackages contain translatable /source/,
causing the named package and its subpackages to be added to the /source
path/. Only files found on the source path are candidates to be
translated into JavaScript, making it possible to mix client-side
and server-side
code together in the same classpath without conflict.

so the behavior looks inconsistent with the documentation (bug?)

What do you think?

Vassilis Virvilis

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment