davidburstrom

Is it an option for you to run the container without the `-p` option (which is the one that resets the permissions)?

Maybe I'm missing something here, but bumping that dependency would either require the entire Spotless project to be built with JDK 11, or (probably better), to use [Gradle Toolchains](https://docs.gradle.org/current/userguide/toolchains.html) to...

Gated tests are also a requirement, yes. I'm thinking of what's necessary in order to compile against a JDK 11 library, because JDK 1.8 cannot load the classes. Since the...

I'll see tomorrow if I can reproduce the error I got when I tried using jdk 8 and the sortpom dependency.

This is the error I get if I simply bump sortpom-sorter to 3.2.0 and compile with JDK 1.8: https://scans.gradle.com/s/nboe7f5nfngb6/console-log?task=:lib:compileSortPomJava#L4

Right, this seems correct. Other than using Gradle toolchains, any idea how to fix that for `test_npm_8`?

You might want to do something similar to https://github.com/diffplug/spotless/pull/1303 to ensure it's easy to maintain support for multiple versions of KtLint.

Looks like it only works if you don't use a `-Werror` javac argument.

Thanks for the suggestion on `resolutionStrategy`. I've experimented with it, and the main drawback, especially for the version compatibility plugin, is that it becomes a bit clunky to set up...

Caveat lector: These two responses are independent and are attempts at addressing the problem from two different viewpoints. > How we should report using constraints is a little unclear at...