Hi Paul,
Is there a possibility of you sharing the codebase over github and put a
license to it ? I have been working extensively with JsInterOp / TypeScript
cross usage and find your POC interesting and would love to contribute if
its with an open license.
thanks,
Debasish
On Thursday,
(just in case someone read this thread) This problem has already been fixed
in 2.8.0-SNAPSHOT. Thanks.
On Tuesday, October 27, 2015 at 9:17:47 PM UTC+1, Ignacio Baca
Moreno-Torres wrote:
>
> At last!
>
-launcherDir's equivalent for DevMode is -war and is not optional. If you use
DevMode with -noserver then it's equivalent to using CodeServer with
-launcherDir.
You're otherwise right.
Just a note: for people coming from "legacy DevMode" in 2.6, 2.7 didn't change
anything, except their
Hi Thomas -
That was the missing piece. I can now get the automatic re-compile on
browser refresh. However, the launcherDir parameter is only available in
the gwt-maven-plugin:run-codeserver mojo. Doesn't that start Super Dev Mode
directly? I thought that *wasn't* the correct way to do things
Unfortunately, that is not true. A lot of people just need to deal with
native types without any need for exporting their own types to JavaScript
and shared libraries will start accumulating unnecessary code for all of
them if it is enabled by default. We have already seen this Google.
Actually
I agree that if you disable exports you can run into the same problem.
However, I would guess most GWT users would have no reason to turn it off
and in that case it would be consistent. It seems more an optimization for
a use case most people won't have.
On Tuesday, April 12, 2016 at 12:51:12
Nobody maintains the JSR303 emulation. Someone (Danilo) once volunteered,
started working on the upgrade, and then disappeared.
If you don't use client-side validation then you can compile with
javax.validation 1.0 and run with 1.1. The problem then is setting up those
rules in your build, and
