I am curious if anybody using Maven+GWT has tried moving to GWT 1.6
yet. I noticed there is no public repository containing the 1.6
realease only RC, Beta, and Milestones. I can always manually deploy
GWT to our internal repository but it's a bit of a pain.
Also, if anybody is using GWT+Maven who prefers the Codehaus plugin
and who the Google Code GWT-Maven plugin? From what I understand
these two Maven plugins are merging in the long term so that only the
Codehaus plugin will be actively developed.
Finally I would also like to post the following question to the GWT
community. What do you use for setting up your builds? I've always
been of the opinion that a good build system is of cardinal
importance, especially on larger projects. At this time I have seen
the following options...
Hand written Ant file
-Calling the GWT compiler directly
-Maven
-with the codehaus plugin (http://mojo.codehaus.org/gwt-maven- plugin/)
-with the Google Code GWT-Maven plugin (http://code.google.com/p/ gwt-maven/)
-Intellij Idea's built in GWT support
-eclipse with special GWT support (I believe some plugins exist
including the recently released Google one)
-Netbeans gwt4NB (https://gwt4nb.dev.java.net/)
I also believe in the importance of build systems! :)
My company's current project (medium size, about 32,000 lines of code)
uses a handwritten Ant build system. We do, however, use the Maven
Ant tasks to manage our project's external dependencies. In addition
to using Ant in our builds, we also use it for most of our deployment
tasks. We develop on Windows (eclipse) and Linux (command-line and
emacs), and the build system accommodates this.
From our build files, we:
1.) Call the GWT compiler directly.
2.) Massage the output to fit our deployment needs.
3.) Run jetty
4.) Run GWT hosted mode (with --noserver, which then interacts with
the jetty instance from step 3).
In general, I'm pretty happy with the build system. It is flexible
enough for our needs, and is smart enough to build only what it needs
to. It is, however, a large portion of our code base (about 4,000
lines of Ant XML, which is over 10% of the code base).
> I am curious if anybody using Maven+GWT has tried moving to GWT 1.6
> yet. I noticed there is no public repository containing the 1.6
> realease only RC, Beta, and Milestones. I can always manually deploy
> GWT to our internal repository but it's a bit of a pain.
> Also, if anybody is using GWT+Maven who prefers the Codehaus plugin
> and who the Google Code GWT-Maven plugin? From what I understand
> these two Maven plugins are merging in the long term so that only the
> Codehaus plugin will be actively developed.
> Finally I would also like to post the following question to the GWT
> community. What do you use for setting up your builds? I've always
> been of the opinion that a good build system is of cardinal
> importance, especially on larger projects. At this time I have seen
> the following options...
> Hand written Ant file
> -Calling the GWT compiler directly
> -Maven
> -with the codehaus plugin (http://mojo.codehaus.org/gwt-maven- > plugin/)
> -with the Google Code GWT-Maven plugin (http://code.google.com/p/ > gwt-maven/)
> -Intellij Idea's built in GWT support
> -eclipse with special GWT support (I believe some plugins exist
> including the recently released Google one)
> -Netbeans gwt4NB (https://gwt4nb.dev.java.net/)
When we upgrade to GWT 1.6 we will check the codehaus plugin and how
the new Google Eclipse plugin + new app structure can be used in a
more comfortable way.
Regards,
Martin
On Apr 9, 5:03 pm, Benju <b...@fastcastmedia.com> wrote:
> I am curious if anybody using Maven+GWT has tried moving to GWT 1.6
> yet. I noticed there is no public repository containing the 1.6
> realease only RC, Beta, and Milestones. I can always manually deploy
> GWT to our internal repository but it's a bit of a pain.
> Also, if anybody is using GWT+Maven who prefers the Codehaus plugin
> and who the Google Code GWT-Maven plugin? From what I understand
> these two Maven plugins are merging in the long term so that only the
> Codehaus plugin will be actively developed.
> Finally I would also like to post the following question to the GWT
> community. What do you use for setting up your builds? I've always
> been of the opinion that a good build system is of cardinal
> importance, especially on larger projects. At this time I have seen
> the following options...
> Hand written Ant file
> -Calling the GWT compiler directly
> -Maven
> -with the codehaus plugin (http://mojo.codehaus.org/gwt-maven- > plugin/)
> -with the Google Code GWT-Maven plugin (http://code.google.com/p/ > gwt-maven/)
> -Intellij Idea's built in GWT support
> -eclipse with special GWT support (I believe some plugins exist
> including the recently released Google one)
> -Netbeans gwt4NB (https://gwt4nb.dev.java.net/)
I just tried to enable maven dependencies management with google
eclipse plugin and m2eclipse. The plugin complains about project
output folder not set to war/WEB-INF/classes.
I know I can switch my maven project output, but is there any chance
the plugin can be set up to adapt to my project layout in a near
future ? I want to stick to standard maven project layout.
GWT should really take care of beeing well integrated with existing
build tools and plugins. We can not always bend our projects just to
keep GWT tooling happy...
Regards,
Johann
On Apr 10, 7:40 am, maku <martin.k...@gmx.at> wrote:
> When we upgrade to GWT 1.6 we will check the codehauspluginand how
> the newGoogleEclipseplugin+ new app structure can be used in a
> more comfortable way.
> Regards,
> Martin
> On Apr 9, 5:03 pm, Benju <b...@fastcastmedia.com> wrote:
> > I am curious if anybody usingMaven+GWT has tried moving to GWT 1.6
> > yet. I noticed there is no public repository containing the 1.6
> > realease only RC, Beta, and Milestones. I can always manually deploy
> > GWT to our internal repository but it's a bit of a pain.
> > Also, if anybody is using GWT+Mavenwho prefers the Codehausplugin
> > and who theGoogleCode GWT-Mavenplugin? From what I understand
> > these twoMavenplugins are merging in the long term so that only the
> > Codehauspluginwill be actively developed.
> > Finally I would also like to post the following question to the GWT
> > community. What do you use for setting up your builds? I've always
> > been of the opinion that a good build system is of cardinal
> > importance, especially on larger projects. At this time I have seen
> > the following options...
> > Hand written Ant file
> > -Calling the GWT compiler directly
> > -Maven
> > -with the codehausplugin(http://mojo.codehaus.org/gwt-maven- > >plugin/)
> > -with theGoogleCode GWT-Mavenplugin(http://code.google.com/p/ > > gwt-maven/)
> > -Intellij Idea's built in GWT support
> > -eclipsewith special GWT support (I believe some plugins exist
> > including the recently releasedGoogleone)
> > -Netbeans gwt4NB (https://gwt4nb.dev.java.net/)
We were using Maven "because that's what everyone uses", but found
that it did not meet our needs.
* It requires a great deal of configuration to properly build a GWT
project
* The tools to integrate Maven/GWT/Eclipse are always in a state of
flux
* Some of the really nice stuff in Maven (documentation, etc.)
doesn't work well in a GWT project
We switched back to Ant, using Ivy for external dependency management,
and have been much happier. Ivy's dependency "configurations" are
much more flexible than Maven's "scopes", and for a GWT project the
additional flexibility is needed.
On Sun, Apr 12, 2009 at 7:35 PM, Daniel Kurka
<kurka.dan...@googlemail.com>wrote:
> Currently we are trying to update our buildsystem from gwt 1.5 + gwt-maven
> from google code
> We are trying to use the trunk of gwt-maven from codehaus since those two
> plugins are merging.
> We were able to sucessfully compile a gwt project, but we still have some
> open issues.
> Has anyone a working installation of GWT 1.6 and Maven?
Yes (mac os x, during week) linux && zindozs during week.
-- “There are two ways of constructing a software design: One way is to make
it so simple that there are obviously no deficiencies, and the other way is
to make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.”
I use maven and GWT, and I just moved to GWT 1.6.4 they are published
I think in maven central repo, I use the antrun plugin to compile and
run the HostedMode in debug mode, I choose the antrun becase at the
time I started the project the maven gwt plugins where not mature
enough and I had not moved because the antrun is very simple and had
worked very well for me, by the way for those interested in using the
maven structure for GWT 1.6.4 , you have to pass -war /src/main/webapp
to the Compiler and HostedMode app to use the default maven structure
Cheers
Gabriel
On Apr 9, 4:03 pm, Benju <b...@fastcastmedia.com> wrote:
> I am curious if anybody using Maven+GWT has tried moving to GWT 1.6
> yet. I noticed there is no public repository containing the 1.6
> realease only RC, Beta, and Milestones. I can always manually deploy
> GWT to our internal repository but it's a bit of a pain.
> Also, if anybody is using GWT+Maven who prefers the Codehaus plugin
> and who the Google Code GWT-Maven plugin? From what I understand
> these two Maven plugins are merging in the long term so that only the
> Codehaus plugin will be actively developed.
> Finally I would also like to post the following question to the GWT
> community. What do you use for setting up your builds? I've always
> been of the opinion that a good build system is of cardinal
> importance, especially on larger projects. At this time I have seen
> the following options...
> Hand written Ant file
> -Calling the GWT compiler directly
> -Maven
> -with the codehaus plugin (http://mojo.codehaus.org/gwt-maven- > plugin/)
> -with the Google Code GWT-Maven plugin (http://code.google.com/p/ > gwt-maven/)
> -Intellij Idea's built in GWT support
> -eclipse with special GWT support (I believe some plugins exist
> including the recently released Google one)
> -Netbeans gwt4NB (https://gwt4nb.dev.java.net/)
I work in a smallish-medium agile environment (12 developers for 3
teams, ~6 GWT 1.5 projects, of which 3 are actively developed during
an iteration) and we happily use maven to manage our projects'
lifecycles.
We used to compile our GWT app with the gwt-maven-plugin hosted at
google code but we recently moved to the mojo one (the merge between
the 2 plugins is finished as far as I can tell in version 1.1-
SNAPSHOT). The configuration is simpler and environment-agnostic (no
need to specify one profile for each OS, the plugin detects the OS and
sets up the correct dependencies automatically). We use the maven
project structure:
* sources in src/main/java
* unit tests sources in src/test/java
* resources in src/main/resources (including GWT module configuration,
html, css and image files, as well as text bundles (for localization
and such))
* war related files in src/main/webapp (currently only WEB-INF/
web.xml)
We set the GWT compiler to output files to target/gwt and then the war
plugin assembles the war file merging src/main/webapp and the gwt
compiler output. The resulting war is immediately deployable on a
tomcat.
We code in eclipse and let the m2eclipse plugin configure the project.
For debugging we create an eclipse launcher manually for each OS
(normally there's a goal in the gwt-maven-plugin to create a launcher
but we haven't tested it as the launcher doesn't change much over
time), and we add the following to the classpath: the project, the
maven classpath, the src/main/resources folder and the OS specific gwt-
dev jar
It all integrates very nicely and once the project is set up we rarely
think about configuration or building the project (as this is managed
automatically by a hudson build manager which polls the svn and builds
the war and deploys it when necessary). We can really concentrate in
coding with this setup.
I'm currently investigating the effort needed to migrate from GWT
1.5.3 to 1.6.4 and I have encountered some issues, mainly with the new
project structure and the hostedMode configuration. The new hosted
mode works quite differently, it now outputs the resource files
declared in the Module.gwt.xml file to a folder named like the module
(the location of this folder defaults to a folder named war at the
root of the project, but it can be configured with the argument -war)
and it now expects to find the WEB-INF folder and associated web.xml
file on that war folder. Currently I haven't managed to call RPC's due
to this change, but I guess I could configure the maven resources
plugin to copy the WEB-INF folder to the war folder during the process-
resources phase. I'll let you know if this works.
Cheers,
Salvador
PS: If you're interested in the project configuration I described
here, you can check out one of my pet projects at http://code.google.com/p/hellagwt/.
If you need any help with maven-gwt integration, I'll be glad to
answer any questions in this thread.
On Apr 12, 8:51 pm, olivier nouguier <olivier.nougu...@gmail.com>
wrote:
> On Sun, Apr 12, 2009 at 7:35 PM, Daniel Kurka
> <kurka.dan...@googlemail.com>wrote:
> > Currently we are trying to update our buildsystem from gwt 1.5 + gwt-maven
> > from google code
> > We are trying to use the trunk of gwt-maven from codehaus since those two
> > plugins are merging.
> > We were able to sucessfully compile a gwt project, but we still have some
> > open issues.
> > Has anyone a working installation of GWT 1.6 and Maven?
> Yes (mac os x, during week) linux && zindozs during week.
> --
> “There are two ways of constructing a software design: One way is to make
> it so simple that there are obviously no deficiencies, and the other way is
> to make it so complicated that there are no obvious deficiencies. The first
> method is far more difficult.”
I was using a maven plugin (http://gwt-maven.googlecode.com/svn/trunk/ mavenrepo) with GWT 1.5.3 without Hosted Mode (in Linux the hosted
mode gives a firefox browser older and doesn't support gears, for
example), I generate a war and the copy it to a jboss server to test
it. I know that it is not very useful, but it is the problem for linux
users :(
But when I try upgrade to GWT 1.6 it doesn't work: crash in the test
task.
If anybody has the same problem, please contact with me.
I find it somewhat odd that the GWT team does not just create an
official maven plugin. They can program the most amazing Java to
Javascript cross compiler, have the most shiny widgets and speedy RPC
services but if people are left in the dark as to how to build the
bloody thing it will never be used! Who agrees that having a solid,
feature complete Maven plugin from Google would increase adoption of
GWT faster than anything?
I used a great starter application created by Sam Brodkin...
It served as a good starting point for building my application in
Maven2. I use Teamcity for continuous integration which at this early
stage essentially means building the project, running one unit test,
and spitting out an artifact every time the SVN is updated.
> I find it somewhat odd that the GWT team does not just create an > official maven plugin. They can program the most amazing Java to > Javascript cross compiler, have the most shiny widgets and speedy RPC > services but if people are left in the dark as to how to build the > bloody thing it will never be used! Who agrees that having a solid, > feature complete Maven plugin from Google would increase adoption of > GWT faster than anything?
> > Who agrees that having a solid,
> > feature complete Maven plugin from Google would increase adoption of
> > GWT faster than anything?
I think the google team is focusing in the basics first, and that
implies not being able to deliver all the goodies at the same time, I
think it all fits rather nicely with the agile mantra: deliver early,
deliver often. If they tried delivering the Eclipse plugin (and all
other popular IDEs' plugins for that matter) and the maven plugin at
the same time they deliver the actual product (GWT) they couldn't
possibly deliver that often. Not to mention that they don't seem to be
maven people, they're rather ant users, so why not leave it to the
community, in true open source spirit, to build the tools they need,
they even help out when there's something that doesn't work nicely
with our tools (one of the issues resolved in 1.6 was specifically
adressed to allow a nicer maven integration), I don't think we can
possibly ask for more cooperation from them.
> Maybe file an enhancement request?
I totally agree with Jeff, if you think a great maven plugin would
help with adoption, why not try the one from the mojo project (which
is quite nice by the way) and report any issues that you find with it.
I don't think we can have a more official plugin than that (after all,
they're the maven experts, not google )
> > > Who agrees that having a solid,
> > > feature complete Maven plugin from Google would increase adoption of
> > > GWT faster than anything?
> I think the google team is focusing in the basics first, and that
> implies not being able to deliver all the goodies at the same time, I
> think it all fits rather nicely with the agile mantra: deliver early,
> deliver often. If they tried delivering the Eclipse plugin (and all
> other popular IDEs' plugins for that matter) and the maven plugin at
> the same time they deliver the actual product (GWT) they couldn't
> possibly deliver that often. Not to mention that they don't seem to be
> maven people, they're rather ant users, so why not leave it to the
> community, in true open source spirit, to build the tools they need,
> they even help out when there's something that doesn't work nicely
> with our tools (one of the issues resolved in 1.6 was specifically
> adressed to allow a nicer maven integration), I don't think we can
> possibly ask for more cooperation from them.
> > Maybe file an enhancement request?
> I totally agree with Jeff, if you think a great maven plugin would
> help with adoption, why not try the one from the mojo project (which
> is quite nice by the way) and report any issues that you find with it.
> I don't think we can have a more official plugin than that (after all,
> they're the maven experts, not google )
I totally agree on the fact that gwt team should not provide the maven
plugin, the codehaus one can do the job. They should just take care of
beeing able to integrate with any build system.
My problems with the current google eclipse plugin :
* If you enable gwt support on your project, GWT SDK library is
automatically added to the project, event if you already manage your
dependencies with maven. You should be able to configure if you want
the sdk to be included or not.
* The plugin complains about output directory not set to "war/WEB-INF/
classes". We should be able to configure this in order to work in a
standard maven way.
Johann
On 16 avr, 08:50, Murray Waters <murray.wat...@gmail.com> wrote:
> On Apr 16, 12:33 pm, Keith Willard <Keith.Will...@gmail.com> wrote:
> > Where is the snapshot respository where the versions 1.1-SNAPSHOT
> > codehaus gwt-maven-plugin lives? only the 1.0 is in the central
> > repository.
> * If you enable gwt support on your project, GWT SDK library is
> automatically added to the project, event if you already manage your
> dependencies with maven. You should be able to configure if you want
> the sdk to be included or not.
> * The plugin complains about output directory not set to "war/WEB-INF/
> classes". We should be able to configure this in order to work in a
> standard maven way.
Those are pretty good remarks, and worth of opening an issue in the
issue tracker. We could do it the other way round though, and let the
maven plugin configure everything to conform to GWT's expectations,
remember that Googlers are not really maven guys.
Cheers,
Salvador
On Apr 16, 10:09 am, johann_fr <johann.vanack...@gmail.com> wrote:
> I totally agree on the fact that gwt team should not provide the maven
> plugin, the codehaus one can do the job. They should just take care of
> beeing able to integrate with any build system.
> My problems with the current google eclipse plugin :
> Johann
> On 16 avr, 08:50, Murray Waters <murray.wat...@gmail.com> wrote:
> > On Apr 16, 12:33 pm, Keith Willard <Keith.Will...@gmail.com> wrote:
> > > Where is the snapshot respository where the versions 1.1-SNAPSHOT
> > > codehaus gwt-maven-plugin lives? only the 1.0 is in the central
> > > repository.
It would definitely be nice if the Google Eclipse plugin was build
system agnostic, or at least gave you more configuration options.
Maybe we should just file a issue with the Google Eclipse plugin (I
can't find the Google Code project...)?
On Thu, Apr 16, 2009 at 4:33 AM, Salvador Diaz <diaz.salva...@gmail.com> wrote:
>> * If you enable gwt support on your project, GWT SDK library is
>> automatically added to the project, event if you already manage your
>> dependencies with maven. You should be able to configure if you want
>> the sdk to be included or not.
>> * The plugin complains about output directory not set to "war/WEB-INF/
>> classes". We should be able to configure this in order to work in a
>> standard maven way.
> Those are pretty good remarks, and worth of opening an issue in the
> issue tracker. We could do it the other way round though, and let the
> maven plugin configure everything to conform to GWT's expectations,
> remember that Googlers are not really maven guys.
> Cheers,
> Salvador
> On Apr 16, 10:09 am, johann_fr <johann.vanack...@gmail.com> wrote:
>> I totally agree on the fact that gwt team should not provide the maven
>> plugin, the codehaus one can do the job. They should just take care of
>> beeing able to integrate with any build system.
>> My problems with the current google eclipse plugin :
>> Johann
>> On 16 avr, 08:50, Murray Waters <murray.wat...@gmail.com> wrote:
>> > On Apr 16, 12:33 pm, Keith Willard <Keith.Will...@gmail.com> wrote:
>> > > Where is the snapshot respository where the versions 1.1-SNAPSHOT
>> > > codehaus gwt-maven-plugin lives? only the 1.0 is in the central
>> > > repository.
The maven-gwt-plugin from codehaus is looking quite good at this
point. I recommend trying 1.1-SNAPSHOT.
I just reported an issue with running unit tests (which has been fixed
in SVN, waiting on a new SNAPSHOT build). With that it does absolutely
everything I've expected (on all platforms, without local
configuration) and with very minimal setup (add the plugin, add a
dependency on gwt-user, done).
The one remaining issue is the new build output format (WAR), and how
resources are deployed. I'm totally against having GWT compile
directly into /src/main/webapp. It's completely against the principles
of keeping your source tree clean and putting all artifacts under
target. If you stick with traditional maven approach, it means you
need to execute war:exploded first before launching hosted mode (and
again if you want to change something without restarting the hosted
mode).
The other approach is stick with src/main/webapp and make sure the
clean plugin cleans out all GWT generated files. Again, this is really
not the right approach :-(
On Apr 16, 8:48 am, Arthur Kalmenson <arthur.k...@gmail.com> wrote:
> It would definitely be nice if the Google Eclipse plugin was build
> system agnostic, or at least gave you more configuration options.
> Maybe we should just file a issue with the Google Eclipse plugin (I
> can't find the Google Code project...)?
> --
> Arthur Kalmenson
> On Thu, Apr 16, 2009 at 4:33 AM, Salvador Diaz <diaz.salva...@gmail.com> wrote:
> >> * If you enable gwt support on your project, GWT SDK library is
> >> automatically added to the project, event if you already manage your
> >> dependencies with maven. You should be able to configure if you want
> >> the sdk to be included or not.
> >> * The plugin complains about output directory not set to "war/WEB-INF/
> >> classes". We should be able to configure this in order to work in a
> >> standard maven way.
> > Those are pretty good remarks, and worth of opening an issue in the
> > issue tracker. We could do it the other way round though, and let the
> > maven plugin configure everything to conform to GWT's expectations,
> > remember that Googlers are not really maven guys.
> > Cheers,
> > Salvador
> > On Apr 16, 10:09 am, johann_fr <johann.vanack...@gmail.com> wrote:
> >> I totally agree on the fact that gwt team should not provide the maven
> >> plugin, the codehaus one can do the job. They should just take care of
> >> beeing able to integrate with any build system.
> >> My problems with the current google eclipse plugin :
> >> Johann
> >> On 16 avr, 08:50, Murray Waters <murray.wat...@gmail.com> wrote:
> >> > On Apr 16, 12:33 pm, Keith Willard <Keith.Will...@gmail.com> wrote:
> >> > > Where is the snapshot respository where the versions 1.1-SNAPSHOT
> >> > > codehaus gwt-maven-plugin lives? only the 1.0 is in the central
> >> > > repository.
> I'm totally against having GWT compile
> directly into /src/main/webapp. It's completely against the principles
> of keeping your source tree clean and putting all artifacts under
> target. If you stick with traditional maven approach, it means you
> need to execute war:exploded first before launching hosted mode (and
> again if you want to change something without restarting the hosted
> mode).
I think your remarks are worth for filing a new issue. Somewhere in
the 1.6 announcement, Googler Miguel Méndez asked "What aspects would
you need to be able to change in order to make the plugin more Maven
friendly? " (http://groups.google.com/group/Google-Web-Toolkit/msg/ 9a3b994595f129db)? Yours is a pretty good response to that question.
One of the big wins with Maven is the "rigid" directory structure,
where source files of all stripes are in src/ and build outputs are in
target/. It's good practice because it doesn't allow for intermingling
source files and build files.
The new GWT war/ dir next to src/ problematic because you have to be
careful how you clean up. I can see many an "aaargh!" being screamed
out in the early morning hours when a tired developer discovers a bug
in her ant script, or when he trashes the war/ dir accidentally.
I would much rather have seen src/java and src/war (better yet, src/
webapp) and the HostedMode compiler would copy src/webapp to war/
before compilation. It would be a whole lot safer and wouldn't really
cost that much, even for large projects with a whole lotta webapp/**
> The one remaining issue is the new build output format (WAR), and how
> resources are deployed. I'm totally against having GWT compile
> directly into /src/main/webapp. It's completely against the principles
> of keeping your source tree clean and putting all artifacts under
> target. If you stick with traditional maven approach, it means you
> need to execute war:exploded first before launching hosted mode (and
> again if you want to change something without restarting the hosted
> mode).
I totally agree here. The "old" GWt build proceding was naive and we
needed twirks to get it running. When I first heard of the new
structure I was really happy: GWT is growing up! But than I had a
closer look at it and I could not believe it! How can the GWT
developer be so genious and so naive at the same time??? How could
they miss that point? Don't they use their own dog food? Did they
never see how projects are build outside? Or do they use something we
don't know?
It is hard to argue to get resources/ time/ budget for a build
infrastructure change.
We need budget now, because GWT 1.6 does it differently - and you know
what? It is naive again! We will need budget again!
We will probably need to wait for GWT 1.7, GWT 1.8, GWT 1.9, GWT 2.0
to have this issue fixed.
> > The one remaining issue is the new build output format (WAR), and how
> > resources are deployed. I'm totally against having GWT compile
> > directly into /src/main/webapp. It's completely against the principles
> > of keeping your source tree clean and putting all artifacts under
> > target. If you stick with traditional maven approach, it means you
> > need to execute war:exploded first before launching hosted mode (and
> > again if you want to change something without restarting the hosted
> > mode).
> I totally agree here. The "old" GWt build proceding was naive and we
> needed twirks to get it running. When I first heard of the new
> structure I was really happy: GWT is growing up! But than I had a
> closer look at it and I could not believe it! How can the GWT
> developer be so genious and so naive at the same time??? How could
> they miss that point? Don't they use their own dog food? Did they
> never see how projects are build outside? Or do they use something we
> don't know?
> It is hard to argue to get resources/ time/ budget for a build
> infrastructure change.
> We need budget now, because GWT 1.6 does it differently - and you know
> what? It is naive again! We will need budget again!
> We will probably need to wait for GWT 1.7, GWT 1.8, GWT 1.9, GWT 2.0
> to have this issue fixed.
