Open GoogleCodeExporter opened 9 years ago
Ideally, you should be doing your changes; testing; debugging everything in your
hosted moded. Since GWT Compiler is actually a long running process, not
everyone
wants the GWT Compiler be invoked for *every* save.
The workaround would be to republish the project.
In case if more number of people request this feature, I'll add it. I'm keeping
this
issue open till then.
Original comment by grprakash
on 22 Jun 2008 at 1:16
I have a similar problem:
0. "Invoke when publishing to an external server" option is *not* selected and
my
project consists of multiple GWT modules.
1. I clean/build and deploy the GWT-project to JBoss, everything works fine.
2. I change a line in the client side code.
3. Whatever I do, I can't get the "module" that has the changed code get built
(via
invoking refresh/build etc.). So nothing gets republished.
4. To get the build done, I either clean/build the entire project (which invokes
gwtBuilder :) or, I open the hosted mode for the given module, press the
compile/browse button see the changes in a browser and then I refresh my
project (so
that build/gwtOutput folder gets updated) and then I can republish.
The issue here is that, I don't want the GWT Compiler invoked at *every* save,
but I
want to be able to invoke it on a single module when I want to.
Original comment by onur.ozorhan@gmail.com
on 26 Jul 2008 at 8:45
> 0. "Invoke when publishing to an external server" option is *not* selected
and
> my project consists of multiple GWT modules.
If you have selected this, then it should work fine. GWT compiler won't be
invoked
for every save, but whenever you say Publish, it would be invoked.
Original comment by grprakash
on 28 Jul 2008 at 11:35
Hi grprakash, I am aware that when the option you mention is selected GWT
compiler
will be invoked with publish. And the feature you're describing works perfectly
well.
But the issue here is, my GWT application consists of multiple modules (module
count
was 11 last time I looked). When I select that feature, gwt-compiler is invoked
for
*all* the modules in the project.
Even though I have a relatively high end developer machine, this compilation
takes
more than 5 minutes.
I guess these two would be good features to have:
1. invoking gwt-compiler for only the modified modules when publishing
2. letting the user explicitly call the gwt-compiler for the modules he prefers
Original comment by onur.ozorhan@gmail.com
on 28 Jul 2008 at 11:49
Option 1 will be little hard, as I can't keep track of the modules which are
changed
or rather I don't know how to say whether a file belongs to a particular module.
Option 2 sounds good to me. Will try how to implement this. I'm spawning off a
different bug for that to track.
Original comment by grprakash
on 28 Jul 2008 at 3:41
Hi, the option 2 (letting the user explicitly call the gwt-compiler for the
modules
he prefers) has been implemented?
Original comment by magno...@gmail.com
on 12 Jun 2009 at 10:17
Original issue reported on code.google.com by
bsel...@gmail.com
on 13 Jun 2008 at 4:03