It was Dale who worked on migrating Geode to use JUnit 5. I know he ran
into some issues but I don't recall what they were. I'm definitely up for
helping on the JUnit 5 front!

On Fri, Jun 26, 2020 at 11:30 AM Jacob Barrett <jabarr...@vmware.com> wrote:

> If the effort to do both is less than the sum of each individually then I
> say lets do it.
>
> Kirk, I recall you putting some effort into JUnit 5 at some point.
>
> -Jake
>
>
> > On Jun 26, 2020, at 11:13 AM, Jens Deppe <jde...@vmware.com> wrote:
> >
> > A bigger effort (but I think more correct and sustainable) would be to
> switch to junit 5 where something like this could more easily be
> implemented.
> >
> > --Jens
> >
> > On 6/26/20, 9:11 AM, "Robert Houghton" <rhough...@vmware.com> wrote:
> >
> >    The plugin code that spawns junit test workers on containers needs
> some serious help. Aside from the benefit we would get on windows, we also
> are blocked on getting to the next major version of Gradle with the current
> tool. I really think it might be easier to write our own Gradle plugin at
> this point.
> >
> >
> >    From: Jacob Barrett <jabarr...@vmware.com>
> >    Date: Thursday, June 25, 2020 at 12:26 PM
> >    To: dev@geode.apache.org <dev@geode.apache.org>
> >    Subject: Docker on Windows
> >
> >> On Jun 25, 2020, at 12:23 PM, Jens Deppe <jde...@vmware.com> wrote:
> >> It's been a couple of years since Sai and I tried (but failed) to
> dockerize the tests. I'm sure docker support has improved and it might be
> worth trying that again.
> >
> >    Docker on windows has improved a lot but wasn’t the major issue the
> docker plugin for Gradle needed some serious work?
> >
> >    I have recently been experimenting with the Docker/Kubernetes for
> Windows experience. Perhaps we can take another stab at this issue.
> >
> >    -Jake
> >
>
>

Reply via email to