sharing gwt-ext's 'public' directory between two modules

[alexzakharov]

I have two modules in my app - mod1 and mod2 and I want to use gwt-ext in both. I can, of course, configure each one individually for gwt-ext and everything will work. However then js\ext resides in the public directory of each module - not ideal.

My first idea was to move out gwt-ext public resources into a separate directory accessible by both modules but this doesn't work since <public> directive of a module can only refer to subdirectories of the module in question, and not to the directory located 'higher up' in package structure.

Using module inheritance seemed like a better idea. So I start out with mod1 and mod2 (not configured for gwt-ext) then I added mod3 that IS configured for gwt-ext. Then I inherit mod1 from mod3, hoping to pickup all gwt-ext related stuff in the process. If I do that I can then compile and run mod1 fine.The problem is that when I switch to 'design' mode of mod1 I get

WindowBuilder internal error
WindowBuilder encountered unexpected internal error. Please contact support.
java.lang.OutOfMemoryError: Java heap space

(This is very easy to duplicate).

So, two questions I guess:
- In general does the designer support module inheritance within same project?
- With regards to gwt-ext, what is the preferred way of avoiding to add ex\gs directory to each module that needs it?

Any thoughts/suggestions would be much appreciated.

[Eric Clayberg]

java.lang.OutOfMemoryError: Java heap space
Any thoughts/suggestions would be much appreciated.

GWT compilation requires a lot of memory, especially when you include additional widget libraries such as GWT-Ext.

That error indicates that you need to increase the heap available to Eclipse.

[alexzakharov]

yeah... my apologies - that was truly idiotic on my part: after i rebooted my 3GB ram box, the error went away. on thursday i was so convinced that the error was a result of internal recursion problem i didn't bother to take the exception at its face value.

[Eric Clayberg]

I'm glad it's working for you. Keep in mind that it is the amount of memory allocated to Eclipse (in the eclipse.ini file) and not the amount on your machine that is important.