Thomas,
thanks. You were spot on.
I am using gwt-tour whch requires ahome-come which was masking
UiBinderParser and UiBinderGenerator.
I have fixed (in my private git) some issues of the same type from eclipse
through the normal java compilation.
SDM was working
GWT compiling was failing
Now
On Friday, April 15, 2016 at 10:15:30 AM UTC+2, Jens wrote:
>
> Well then you have a class path issue. The classpath of your CodeServer
> run configuration is probably different than the one used for a normal
> compile. Make sure you do not have GWT 2.7 on classpath.
>
…or a third-party lib th
Well then you have a class path issue. The classpath of your CodeServer run
configuration is probably different than the one used for a normal compile.
Make sure you do not have GWT 2.7 on classpath.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
User
Hi Jens
I would prefer a trick in the opposite direction (make compile work instead
of breaking SDM) but even that fails :-)
SDM continues working after the 'clean'. Production compile fails with this
message.
I noticed that UibinderWriter has an added gssOptions parameter in the
constructor. Loo
Yes it can happen that SDM works but a production compile fails. For me its
pretty rare but it can happen. I guess there are some difficult to spot
bugs within incremental compilation of SDM.
You can clean SDM caches by launching SDM, open its site (localhost:9876)
and hit the small clean butto
This is probably due to my setup...
Before I post the embarrassing details and waste everybody's time...
* I have build gwt from git. Check
* I have SDM working with my code. Check
* Normal ant build / compilation of my program fails due to memory. Add
more memory. Check
Q: Now the compilation
