I have a library project (gwt-lib) containing a few emulated JRE classes.
The emulated classes work just fine in my gwt-app project but I would like
to have formal unit tests for them.
I'm using tbroyer's gwt-maven-plugin and have the emulated classes in
src/main/super.
Since these are JRE emu
On Tuesday, February 12, 2019 at 4:10:42 PM UTC-5, Jens wrote:
>
> You have to create a a subclass of GwtTestCase which requires you to
> specify a GWT module.
>
> Here an example for java.util.Random emulation within GWT SDK:
> https://github.com/gwtproject/gwt/blob/master/user/test/com/google/
On Wednesday, February 13, 2019 at 2:47:10 PM UTC-5, Jens wrote:
>
>
> This can be used to super source classes for GWT compiler that you only
> use within GwtTestCase and not in your normal app code, e.g. some test
> library that only works with GWT if you super source some classes.
>
>
Thank
It's a slightly off-topic question but possibly an issue familiar to GWT
developers.
I'm using Dagger2 and AutoFactory and am quite happy with both. Eclipse,
however, does not play nicely with them. After saving any change, I will
usually end up with a broken build because Dagger doesn't genera
On Saturday, February 23, 2019 at 7:03:49 AM UTC-5, Thomas Broyer wrote:
> Eclipse annotation processing is known to be broken in many ways...
>
Yep. I took a look at the logs as Jens suggested and found an exception
from the dagger compiler. Eclipse is definitely not doing it right. The
dagger
I created an issue in github for an possible validation related bug.
https://github.com/gwtproject/gwt/issues/9654
I'm trying to get hibernate-validator 6.0.X to work and have run into an
issue and am not sure if what I'm seeing in the GWT codebase is a bug or
not.
I'm using Validator.validate
