Comment on WAR_Design_1_6 in google-web-toolkit

[codesite...@google.com]

Comment by atifijazkhan:

A quick question about 1.1 "A generated selection script is copied into
war/qualified.ModuleName/"

Will the folder for a module will always be created in the "war/"
directory? What if the Launch html file is not in the root "war/"
directory but is in another subdirectory?

Currently I see no option to specify the location for the module specific
directory.

For more information:
http://code.google.com/p/google-web-toolkit/wiki/WAR_Design_1_6

[codesite...@google.com]

Comment by sco...@google.com:

It will always be put into root war directory, there's currently not an
option to deploy deeper.

[codesite...@google.com]

Comment by matthew.mceachen:

If you have your compiled artifacts get copied directly into "war/"
alongside checked in files, how do you implement a "clean" target?

This has been solved before -- have a "source" war
directory, "src/main/webapp/" (maven-style), have your war target copy the
static files into a staging directory ("target/war/" or whatever), and plop
the compiled artifacts there too.

[codesite...@google.com]

Comment by sco...@google.com:

That's correct, a more advanced setup would involve having a "source" war
folder and copying it's contents into a "target" war folder; the GWT
compiler would output into the "target" war folder, and you could clean
just by blowing away the whole folder.

[codesite...@google.com]

Comment by mar...@myd0.de:

I just played a bit with the gwt-maven-plugins from the Codehaus Mojo.
Hosted Mode works after running `mvn war:inplace`, but that's not a very
elegant solution. It would be better if there was a command line option to
pass extra classpath folders to Jetty. The jetty-maven-plugin has a
parameter like that:
`<extraClasspath>target/classes</extraClasspath>`
That would also make a multi-module setup possible...

[codesite...@google.com]

Comment by mar...@myd0.de:

The extraClasspath is configurable with web-jetty.xml. But the file isn't
loaded. Is this a limitation of GWT or a bug?

[codesite...@google.com]

Comment by mar...@myd0.de:

Got web-jetty.xml working. Hosted Mode still misses to classes ... :-/
With an external jetty everything works fine...

[codesite...@google.com]

Comment by mar...@myd0.de:

Just tested with Spring: ClassNotFoundException
Then I moved the classes in the GWT samples into a external target folder
and copied my web-jetty.xml into war/WEB-INF. Started the Hosted mode with
Ant: Everything works fine. Seems like a classpath problem with Maven.
Should be solvable...

[codesite...@google.com]

Comment by mar...@myd0.de:

Sorry, forgot that the build.xml compiles the classes on "ant hosted".
Without the compile task it isn't working... :-/
The problem still exist and can currently only be solved be copying classes
and libs into a central war folder. But this isn't nessesary. Jetty is
flexible enough to handle this issue better...
I still don't get why the classpath isn't working. This was not an issue
with Tomcat...

[codesite...@google.com]

Comment by sco...@google.com:

We're considering relaxing the constraints. See issue #3435.