Re: GWT 2.7.0 DevMode not allowing multiple GWT Modules

2015-05-03 Thread tbb 
SDM is in the pipeline Thomas.
For now, I've gone down the path of adding a 2nd Maven module which uses 
the buildhelper plugin to get the resources. Not nice, but does the job 
until we move over to SDM.

By the way, is there any timeframe for GWT 3 yet? ;) Having a stable 
JsInterop API would safe quite a bit.

Cheers,
Thomas

On Sunday, May 3, 2015 at 5:30:15 PM UTC+8, Thomas Broyer wrote:



 On Sunday, May 3, 2015 at 3:57:13 AM UTC+2, tbb wrote:

 Thanks Thomas.

 I might give that a try, but even if it worked, it would still be a 
 pretty clunky. Anyway chance that could be easily fixed?


 Classic DevMode is very unlikely to receive any fix. Patches would 
 probably be accepted though, but it's only a matter of time before 
 classic DevMode is completely removed from the codebase (GWT 3.0?) so I 
 wouldn't invest time fixing it and would rather put it into switching to 
 SDM if I were you.


-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7.0 DevMode not allowing multiple GWT Modules

2015-05-03 Thread Thomas Broyer 


On Sunday, May 3, 2015 at 3:57:13 AM UTC+2, tbb wrote:

 Thanks Thomas.

 I might give that a try, but even if it worked, it would still be a pretty 
 clunky. Anyway chance that could be easily fixed?


Classic DevMode is very unlikely to receive any fix. Patches would 
probably be accepted though, but it's only a matter of time before 
classic DevMode is completely removed from the codebase (GWT 3.0?) so I 
wouldn't invest time fixing it and would rather put it into switching to 
SDM if I were you.

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7.0 DevMode not allowing multiple GWT Modules

2015-05-02 Thread Thomas Broyer 
IIRC this could be due to a cache expiration in the mapping from module 
short names (e.g. portal) to their fully-qualified name (e.g. 
com.xyz.ModuleB).
One workaround *could* be to load both modules fast enough after DevMode 
startup that the mapping is not reclaimed.

On Saturday, May 2, 2015 at 10:04:25 AM UTC+2, tbb wrote:

 I've migrated a Maven based GWT project from GWT 2.5 to 2.7. The project 
 has 2 GWT Modules (.gwt.xml) within one Maven project. In GWT 2.5 I was 
 able to start DevMode and point the browser to the host page of either 
 module and all worked fine.

 My POM looked like this:

 runTarget${gwt.hostPageModuleA}/runTarget
 modules
 modulecom.xyz.ModuleA/module
 modulecom.xyz.ModuleB/module
 /modules

 Now with GWT 2.7 (still using classic DevMode), DevMode only works for 
 the module which has its hostPage configured as runTarget. If I switch the 
 hostPage to moduleB, moduleB works.

 If I'm accessing the module which is not matching the runTarget, I'm 
 getting this error message:

 00:01:19.009 [ERROR] Unable to find 'portal.gwt.xml' on your classpath; could 
 be a typo, or maybe you forgot to include a classpath entry for source?

 Once the runTarget points to the right host page (i.e. restart with a 
 different profile), it works fine.

 Rather cumbersome for me as I'm working on both GWT modules at the same 
 time - I now have to stop DevMode, select another Maven profile which 
 adjusts the hostPage and then start again.

 How can I make that work with GWT 2.7 (and not switch to SuperDevMode)?

 TIA

 Thomas


-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT 2.7.0 DevMode not allowing multiple GWT Modules

2015-05-02 Thread tbb 


I've migrated a Maven based GWT project from GWT 2.5 to 2.7. The project 
has 2 GWT Modules (.gwt.xml) within one Maven project. In GWT 2.5 I was 
able to start DevMode and point the browser to the host page of either 
module and all worked fine.

My POM looked like this:

runTarget${gwt.hostPageModuleA}/runTarget
modules
modulecom.xyz.ModuleA/module
modulecom.xyz.ModuleB/module
/modules

Now with GWT 2.7 (still using classic DevMode), DevMode only works for 
the module which has its hostPage configured as runTarget. If I switch the 
hostPage to moduleB, moduleB works.

If I'm accessing the module which is not matching the runTarget, I'm 
getting this error message:

00:01:19.009 [ERROR] Unable to find 'portal.gwt.xml' on your classpath; could 
be a typo, or maybe you forgot to include a classpath entry for source?

Once the runTarget points to the right host page (i.e. restart with a 
different profile), it works fine.

Rather cumbersome for me as I'm working on both GWT modules at the same 
time - I now have to stop DevMode, select another Maven profile which 
adjusts the hostPage and then start again.

How can I make that work with GWT 2.7 (and not switch to SuperDevMode)?

TIA

Thomas

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7.0 DevMode not allowing multiple GWT Modules

2015-05-02 Thread tbb 
Thanks Thomas.

I might give that a try, but even if it worked, it would still be a pretty 
clunky. Anyway chance that could be easily fixed?

Right now, I'm leaning towards a second Maven module - using the 
buildhelper plugin to mirror the source paths of the other module in...

On Saturday, May 2, 2015 at 6:02:05 PM UTC+8, Thomas Broyer wrote:

 IIRC this could be due to a cache expiration in the mapping from module 
 short names (e.g. portal) to their fully-qualified name (e.g. 
 com.xyz.ModuleB).
 One workaround *could* be to load both modules fast enough after DevMode 
 startup that the mapping is not reclaimed.

 On Saturday, May 2, 2015 at 10:04:25 AM UTC+2, tbb wrote:

 I've migrated a Maven based GWT project from GWT 2.5 to 2.7. The project 
 has 2 GWT Modules (.gwt.xml) within one Maven project. In GWT 2.5 I was 
 able to start DevMode and point the browser to the host page of either 
 module and all worked fine.

 My POM looked like this:

 runTarget${gwt.hostPageModuleA}/runTarget
 modules
 modulecom.xyz.ModuleA/module
 modulecom.xyz.ModuleB/module
 /modules

 Now with GWT 2.7 (still using classic DevMode), DevMode only works for 
 the module which has its hostPage configured as runTarget. If I switch the 
 hostPage to moduleB, moduleB works.

 If I'm accessing the module which is not matching the runTarget, I'm 
 getting this error message:

 00:01:19.009 [ERROR] Unable to find 'portal.gwt.xml' on your classpath; 
 could be a typo, or maybe you forgot to include a classpath entry for source?

 Once the runTarget points to the right host page (i.e. restart with a 
 different profile), it works fine.

 Rather cumbersome for me as I'm working on both GWT modules at the same 
 time - I now have to stop DevMode, select another Maven profile which 
 adjusts the hostPage and then start again.

 How can I make that work with GWT 2.7 (and not switch to SuperDevMode)?

 TIA

 Thomas



-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.