Hi Jen,
I have changed my entry point to
class='com.cname.proj.client.Main. But now super devmode is now giving
me an error not able to find com/cname/proj/client/Main.gwt.xml in the
classpath. It forces me to keen Main.gwt.xml and Main.java in the same
folder/package and then it is giving me
> Content in Main.gwt.xml
>
>
>
>
>
>
>
>
>
>
>
>
With that configuration the GWT compiler can see packages
com.cname.proj.client and com.cname.proj.service in your main project.
However your entry point is not in any of these
Really good job, thanks to everyone involved!
On Thursday, June 23, 2022 at 7:16:50 PM UTC+3 nilo...@gmail.com wrote:
> I'm very happy to announce the release of GWT 2.10.0. This is the first
> release using our new groupId, org.gwtproject, and the final release using
> com.google.gwt. If you
Hello all
I use legacy dev mode with a old FF17 with succes on GWT 2.10 / jdk 11. I
had to overide JettyLauncher class to add "javax.sql." on the
"allowedFromSystemClassLoader" variable
Until now, I have no issue with this mode except this.
Le jeu. 30 juin 2022 à 09:30, Thomas Broyer a écrit :
On Thursday, June 30, 2022 at 4:22:08 PM UTC+2 mmo wrote:
> Pardon my ignorance but I never had to dive very deeply into many of these
> GWT details and options, yet.
>
> Is that "-strict" that Michael and you mention the same as setting:
>
> gwt-maven-plugin
>
I am using GWT 2.9.0 + GXT 4.1.0 + Java 11 combination. I am getting below
error *[ERROR] Hint: Your source appears not to live underneath a
subpackage called 'client'; no problem, but you'll need to use the
directive in your module to make it accessible ProjectName*. Below is my
project
after cleaning up my projects a bit, migration from 2.9 completely
transparent - great job!
On Monday, June 27, 2022 at 10:25:28 PM UTC+2 RT wrote:
> Great to see this progress. Updated my project to 2.10 from 2.9, the only
> issue so far was removing the ie10 user agent in the gwt.xml,
>
