Closed dnouls closed 9 months ago
It turns out that there is a problem with assertions in GWT 2.9/2.10 due to changes in JDT. There will be a fix when the patch gets merged and a newer GWT is released.
In the meantime it would be smart to refrain from using that ternary operation in the DateTimeFormatterBuilder@LocalizedPrinterParser::toString method. It seems that you were already aware of this AST error problem some time ago since I saw you linked to this bug with a previous commit: https://github.com/gwtproject/gwt/issues/9694
Yes, I am already aware of this issue. Unfortunately, it is not a single place in the code that affected by this issue. So, for existing versions of GWT (2.9.0/2.10.0) I suggest to use the workaround - disable JVM asserts as it suggested in https://github.com/gwtproject/gwt/issues/9694.
I will update the readme to mentioned that.
I have a large project where I am trying to migrate to GWT 2.10.0. We are depending on gwt-beans-validator, which is now depending on gwt-time 2.0.10.
For some reason I cannot even compile a simple utility library and run the GWTTestCases there. When trying to run the GWTTestCase I get the following compiler exception:
When I run the debugger and put a breakpoint when this exception happens, I see that it is seems to be related to compiling DateTimeFormatterBuilder$LocalizedPrinterParser::toString
Is this a known issue ?