I was too quick to declare victory.
I did not realize that I was no longer building with GWT 2.9.0 due to a bad
merge my pom was overwritten with 2.8.2 again.
But what you just wrote helped indeed. I was still using jsinterop-base
1.0.0-RC1 and jsinterop-annotations 1.0.0.
Thanks for the
I switched from GWT 2.8.2 to GWT 2.9.0 and I get some GWTC compilation
errors when compiling with certain generic constructs.
It compiles fine with JDK11 and in IntelliJ, but GWTC no longer seems to
support this:
[INFO] --- gwt-maven-plugin:1.0.0:compile (default-compile) @
Interestingly, I've run into exactly the same issue yesterday, but other way
around: my code compiles in GWT 2.9 (and javac and Eclipse), but not in GWT
2.8.2 which refuses to accept parameters for one method with generics-heavy
signature.
I've even explored the possibility to force GWT 2.8.2
Whoops, sorry, I see it in the other thread
"https://groups.google.com/d/topic/google-web-toolkit/aCWkpXWVsD4/discussion;.
On Friday, May 29, 2020 at 9:43:36 AM UTC-5, Colin Alworth wrote:
>
> We did see type inference issues in earlier builds of the JDT version that
> GWT uses, but after an
So the Eclipse JDT version GWT uses has a generics bug then. Have you tried
open the project/code in Eclipse to see if Eclipse complains as well? If
Eclipse does not complain then it is probably fixed and we can likely just
upgrade JDT again in GWT.
-- J.
--
You received this message because
I don't have access to eclipse in my work environment - not allowed.
On Friday, May 29, 2020 at 3:02:00 PM UTC+2, Jens wrote:
>
> So the Eclipse JDT version GWT uses has a generics bug then. Have you
> tried open the project/code in Eclipse to see if Eclipse complains as well?
> If Eclipse
On Friday, May 29, 2020 at 1:55:42 PM UTC+2, David Nouls wrote:
>
>
> Now I have a second problem, this time with some generics that is accepted
> by javac or IntelliJ but GWTC seems to not support it.
>
Same here (on a third-party lib that hasn't been maintained for nearly 2
years )
--
You
We did see type inference issues in earlier builds of the JDT version that
GWT uses, but after an update was done we thought that the issues were
resolved.
Can you give an example so we can check to see if JDT has handled this in a
later update that we can migrate to?
On Friday, May 29, 2020
Sorry, I created a different topic since I did not want to mix 2 problems
in one group chat.
On Friday, May 29, 2020 at 4:44:46 PM UTC+2, Colin Alworth wrote:
>
> Whoops, sorry, I see it in the other thread "
> https://groups.google.com/d/topic/google-web-toolkit/aCWkpXWVsD4/discussion
> ".
>
>
Log of the error in our project:
Tracing compile failure path for type
'org.waveprotocol.wave.model.supplement.WaveletBasedSupplement'
[ERROR] Errors in
I changed my maven pom to select 3.20.0 of org.eclipse.jdt:ecj as that
seemed to be the only dependency from eclipse.jdt.
But the compilation still failed with the same error.
I also tried 3.21.0 but there the compilation does not seem to ever finish
(cpu usage goes to 0%).
On Friday, May 29,
11 matches
Mail list logo
