The build is failing again, two days in a row, and since this is shortly
after the jsinterop-annotation change, there is concern that this failure
is a result of that change. Can a googler look into this, or grant us the
ability to do so?
Thanks,
Colin
On Monday, July 22, 2019 at 12:48:34 PM U
On Sunday, May 3, 2020 at 3:37:30 PM UTC+2, Colin Alworth wrote:
>
> The build is failing again, two days in a row, and since this is shortly
> after the jsinterop-annotation change, there is concern that this failure
> is a result of that change. Can a googler look into this, or grant us the
Yes - I've grown accustomed to the emails being too truncated to be helpful,
but I do have that set of tests fixed, and am slowly running the other tests in
the build to be sure that I haven't broken anything else. This shouldn't affect
the gwt distribution artifacts, provided all tests pass, bu
Am Montag, 20. April 2020, 03:01:12 CEST schrieb Colin Alworth:
> That said, validation is basically the only thing that _isn't_
> ready for j2cl, and there is a small gwt-validation project that has gotten
> started that is compatible with both gwt2 and j2cl - do you have plans to
> finish https:/
Excellent - reach out in https://gitter.im/gwtproject/gwt,
https://gitter.im/gwtproject/gwt-modules, or https://gitter.im/vertispan/j2cl
for any discussion around this, and people who are eager to help test.
--
Colin Alworth
co...@colinalworth.com
On Sun, May 3, 2020, at 11:40 AM, Manfred
I'll have a look at the Jenkins configuration tomorrow.
On Sun, May 3, 2020 at 6:37 AM Colin Alworth wrote:
> The build is failing again, two days in a row, and since this is shortly
> after the jsinterop-annotation change, there is concern that this failure
> is a result of that change. Can a g
