Daniel Lacasse

We should provide a basic interface type that users can use to declare JDK testing which we can use to provide warnings when a JDK is not supported by Gradle....

I'm still not set if we would want to introduce lifecycle tasks for all test suites when multiple testing strategies are available. The reason being if the testing strategy composes...

Converting the `test` task into a `NO-SOURCE` lifecycle task is a sensible default for that specific corner case.

We need to be careful here :-)... We have to make sure the `test` task doesn't end up being reused. For example, if a testing strategy name is an empty...

Shimming the plugin entry point works great except when the incompatibility is with the Gradle metadata. Either we warn against using it (which may not be a great idea) or...

When fixing this, we should consider warning when a user configures a lower JVM compatibility version than the minimum JVM for the minimum Gradle version. They most likely want to...

This issue is a bit different than the one we encountered. This one breaks Gradle cacheability when compiling against complicated preprocessor libraries such as Boost. The issue is twofold: 1)...

Nothing to worry about. I'm still working on the project. I was distracted with the Toolbox project for the last two months as I'm trying to make Nokee build more...

Sorry for the longer-than-expected hiatus. I'm still working on the project. My time has been quite heavily dedicated to clients at the moment so the effort has shifted toward samples...

Don't worry, I hope to focus a bit more next month. I'm in the middle of trying to get a sample portal release. With my clients, I built a lot...