Thanks Colin! Indeed the Ant classpath was using the old GWT 2.8.1... My
bad, sorry.
Tiberiu
On Mon, Aug 14, 2023 at 4:33 PM Colin Alworth
wrote:
> Tiberiu, the fact that it works in Eclipse strongly suggests to me that
> the ant classpath is different from the eclipse project classpath. That
Tiberiu, the fact that it works in Eclipse strongly suggests to me that the
ant classpath is different from the eclipse project classpath. That
different configuration will lead to different results. This error is
typically indicative of some other error happening (typically classpath
related)
Hello everyone,
I just upgraded to GWT 2.10.0 from 2.8.1 and I receive the same error when
compiling through an Ant build.
The code and scripts are identical and is compiling just fine with Java
1.8, GWT 2.8.1 and Eclipse 4.17. However with Java 13 or 17, GWT 2.10.0 and
Eclipse 4.28 gives the
See https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
GWT *runs* on JDKs from 8 to 17; you can however only compile Java 11 –at
most– source files (depending on -sourceLevel).
When facing that kind of error, make sure you run with -failOnError (or its
older name: -strict), and
We are using JDK 17 here at the office for builds without any issue.
(Gradle setup here).
On 10/7/22 08:29, Christian Nzhie wrote:
Hello here.
I would like to react for this threat. Would at this time (2022) gwt
supports java 12?
For I am experiencing the error mentioned above.
Thanks in
Hello here.
I would like to react for this threat. Would at this time (2022) gwt
supports java 12?
For I am experiencing the error mentioned above.
Thanks in advance.
On Monday, May 20, 2019 at 12:59:25 AM UTC ma...@craig-mitchell.com wrote:
> I don't believe GWT supports Java 12 yet. I'd
I don't believe GWT supports Java 12 yet. I'd recommend just using Java 8.
And you might want to use the latest GWT version (2.8.2).
--
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
I know, it's been a while, did you find solution to this issue?
On Monday, May 4, 2015 at 1:55:23 PM UTC-7, Danish Khan wrote:
>
> Thanks for your reply, I tried it, but it didn't fix the issue.
>
> On Thursday, April 30, 2015 at 11:16:54 AM UTC-7, Nature Boy wrote:
>>
>> When you are importing
I just had the same error message and it turned out to be my GWTUnit test
classes being named SomeName*Test* instead of *GwtTest*SomeName.
Ending on Test the GWTUnit test classes were picked up by the Surefire
plugin instead of the GWT plugin. Removing the Test postfix and adding the
GwtTest
Thanks for your reply, I tried it, but it didn't fix the issue.
On Thursday, April 30, 2015 at 11:16:54 AM UTC-7, Nature Boy wrote:
When you are importing com.google.gwt.user.User in gwt.xml you are using
single quote instead of double quote. This may be the reason.
On Apr 30, 2015 9:12 PM,
Hi guys,
Any ideas/help with the following issue?
Thanks.
On Thursday, April 23, 2015 at 12:06:15 AM UTC-7, Danish Khan wrote:
Hi all,
I am upgrading to GWT 2.7.0 / Smartgwt 5, and I am seeing the following
error when I try to build it through maven:
[GWT][ERROR] Hint: Check
When you are importing com.google.gwt.user.User in gwt.xml you are using
single quote instead of double quote. This may be the reason.
On Apr 30, 2015 9:12 PM, Danish Khan danishullahk...@gmail.com wrote:
Hi guys,
Any ideas/help with the following issue?
Thanks.
On Thursday, April 23, 2015
12 matches
Mail list logo
