For some reason the combination of the new Eclipse plugin (3.2.2) and the
new GWT (2.5.1) is not working for me.
Outside eclipse all works fine.
All this worked fine two days ago with the previous plugin (3.2.1) and SDK
(2.5).
I'll appreciate any suggestions.
-- Reuben
On Monday, March 11,
Fast forward to February 2013, I am having the exact same problem but only
when compiling in dev mode and only if doing so from eclipse...
On Tuesday, July 3, 2012 5:06:38 PM UTC-4, Matthew Wiley wrote:
Thanks for pointing this out. I had the exact same problem.
On Wednesday, December 14,
Which again got resolved by rearranging the project classpath.
Thanks.
On Wednesday, February 13, 2013 4:10:38 PM UTC-5, Reuben S wrote:
Fast forward to February 2013, I am having the exact same problem but only
when compiling in dev mode and only if doing so from eclipse...
On Tuesday
We have a number of fairly large GWT/GXT screens in our application,
most of them run 'embedded' in our application main window, which
includes a mix of 'legacy' client code and areas of GXT code.
Navigating to and away from pages containing GWT code does not show
any significant memory leaks in