Re: best practices for modular GWT app

> My recommendation, do NOT create a maven module if you don't need it (I > think that you do not need it). > +1. Right. I would only split my client side code into multiple maven modules if I want to share client side code with a different project. If you don't do that, then adding

Re: [gwt-contrib] Re: Errors in com/google/gwt/emul/java/lang/String.java

FTR, answered in gwt users forum: https://groups.google.com/d/topic/google-web-toolkit/OWaNMLLdwbQ/discussion On Thursday, October 13, 2016 at 7:41:26 PM UTC+2, Roberto Lublinerman wrote: > > You probably have a misconfigured class path. The symptoms are consistent > with trying to compile

Re: [gwt-contrib] Re: Errors in com/google/gwt/emul/java/lang/String.java

You probably have a misconfigured class path. The symptoms are consistent with trying to compile rc3 GWT SDK emulation library with an rc2 compiler. On Thu, Oct 13, 2016 at 10:05 AM, Teletin Alin wrote: > Forgot to say that with: >> > The pom.xml versions for gwt: >

Re: Errors in com/google/gwt/emul/java/lang/String.java

The problem is that you have a mix of rc2 and rc3 libs in your classpath, and this is because org.codehaus.mojo:gwt-maven-plugin itself brings GWT dependencies (with the same version as the plugin, as a convention). See

[gwt-contrib] Re: Errors in com/google/gwt/emul/java/lang/String.java

> > Forgot to say that with: > The pom.xml versions for gwt: 2.8.0-rc2-patched 2.8.0-rc2 it works. So, the problem is in rc3. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from

Errors in com/google/gwt/emul/java/lang/String.java

Hi all, I have the following error at compilation: Errors in com/google/gwt/emul/java/lang/String.java [INFO] [ERROR] Line 165: 'String.NativeFunction String.getFromCharCodeFunction()' has invalid name 'String.fromCharCode'. [INFO] [ERROR] Line 165:

Re: best practices for modular GWT app

The IT directory in the gwt-maven-plugin includes more ussage examples, this one includes all possible maven module types https://github.com/tbroyer/gwt-maven-plugin/tree/master/src/it/e2e as described here https://tbroyer.github.io/gwt-maven-plugin/. You do not need to use resources->includes and

Re: A DateBox where I can select the time and hide the DatePicker

it's a vry old thread, but seems many ppl still have the same problem, so regarding 1: begin.getDatePicker().setVisible(false); -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it,

Re: best practices for modular GWT app

I do not know. We don't use "classifier-sources" in our maven files. I never run super-dev-mode from command-line. I run it form within the IDE. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving

[gwt-contrib] Re: GWT 2.8.0 RC3 is here!

> Sorry for bothering you, but what about notes ? > You can look at the commit log for now: https://github.com/gwtproject/gwt/compare/2.8.0-rc2...2.8.0-rc3 -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this

[gwt-contrib] Re: GWT 2.8.0 RC3 is here!

Sorry for bothering you, but what about notes ? четверг, 29 сентября 2016 г., 16:54:46 UTC+2 пользователь Daniel Kurka написал: > > Hi all, > > I just build the GWT 2.8.0 RC3 and pushed it to maven central. The > complete SDK is also available from here . > > Please start

[gwt-contrib] Clean up PRs on gwt-site

What do you think of merging the PRs on the gwt-site? Thanks, Brandon -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: best practices for modular GWT app

> On 12 Oct 2016, at 19:38, Kirill Prazdnikov wrote: > > I do not completely understand which problems do you have, but we dont have > any issues working with SDM with modules I described above. maybe was something wrong in my project layout. Now I made another test, and in