This is a slf4j provider made to write test assertions against.

But there can be only one slf4j provider on your classpath at the same time, otherwise who knows which will be used.

the remal.component-metadata plugin identifies a lot of these sorts of conflicts so they don't happen silently.

but that doesn't have spf4j-slf4j-test in its list of things it knows about, so we also need to specify that.

once you've identified conflicts, you have to resolve them, which takes ten lines for some reason, so I put it in a function.

debugging wasn't working very well on scripts included with `apply from`, and that's how I ended up writing a gradle plugin.

with slight refactor to avoid mocking static method on Thread.

…ibility to satisfy both app and test code.

The more I look at it the more it circles back to the current design.

like `hasItems` but it checks from one collection you pass to it, not each one of a variable number of arguments.

so other tests can use jupiter Extension

We use TestFX so the JavaFX Task has an Application Thread to run in.

Replace the GameStarter Interface with Callable<Process>.

…cess termination

…if it exits with error

We don't want thread cancellation to terminate the process.

…launch success.

…tStream.

 💭 "it'll be easy," they said.

…(or at least try to).

we don't use the annotation parts of spf4j-slf4j-test enough to keep Vintage around

This does is a spec change, but the best way to avoid this "test failure won't show us TRACE output unless we use the @CollectLogs decorator" is to not rely on TRACE output.

Especially since we want game output more visible anyway, for troubleshooting on launch failure.

… of ApplicationController

…le-like interface

…e is set.

Instead of having to re-bind every time we do a new run.

…plementation of isRunning.

https://github.com/TomasMikula/ReactFX/blob/v2.0-M5/reactfx/src/main/java/org/reactfx/util/FxTimer.java

Copyright (c) 2013-2014, Tomas Mikula
licensed under http://opensource.org/licenses/BSD-2-Clause

This makes the dependency graph feel pretty good to me. GameService is responsible for translating Config/Settings to something RunGameTask needs.

otherwise we would need _another_ thread to watch the error stream.

sort of. this thing.

copied from upstream

without this, "quit launcher after start" could be frustrating.

otherwise the logger shows `null`