The dependency issue could be solved separately in a much simpler change.
I agree improvements could be made for 2.8 testing but it is a big project
and I think it might be more worthwhile to have 3.x sooner.
Anyway we can discuss this further after we release the source.
On Fri, Feb 16, 2018 a
Several things I'd like to achieve:
* I'd like to support JUnit 4 in GWT2 (well, I'd actually like to support
JUnit 5 in both, but one step at a time) - JUnit 3 practically doesn't
exist outside of GWT2.
* There are probably better ways to do testing than the existing junit
shell wiring in GWT
I haven't thought about separating it from J2CL, not sure if it is a good
idea.
Why do you need it for GWT2? For code sharing, we simply use Junit3 style
and we didn't feel much pain about it.
On Thu, Feb 15, 2018 at 12:15 PM Colin Alworth wrote:
> Anything we can do to facilitate this? Also, i
>From our discussion in Gitter, it sounds like many/most of the changes in
GoogleMods are no longer needed to get tests to pass - either the existing
tests are insufficient to make sure that these changes are still there, or
the important changes have been folded in upstream.
I do recall that t
On Friday, February 16, 2018 at 11:42:14 AM UTC+1, Nándor Előd Fekete wrote:
>
> The fix for this bug got backported to the 4.7 line of Eclipse. Will there
> be a 2.8.3 GWT release and do you guys plan to upgrade to this version of
> JDT if so?
>
I don't know when (or whether, but that's likel
The fix for this bug got backported to the 4.7 line of Eclipse. Will there
be a 2.8.3 GWT release and do you guys plan to upgrade to this version of
JDT if so?
On Monday, October 2, 2017 at 10:05:31 AM UTC+2, Ignacio Baca Moreno-Torres
wrote:
>
> Yep, IMO the best compromise between solution &
