Ned Twigg
Ned Twigg
I think you could accomplish the above with ```gradle spotless { enforceCheck env['CI'] != 'true' ```
@helloncode happy to take a PR for this, a new issue is probably better. I will delete my comment here and your comment above at some point to keep this...
Closing due to inactivity.
This is still interesting, but a lot has changed since this was submitted. In particular, our next release bumps bumps us to Java 11 which lets use the latest JGIt....
Published in `plugin-maven 2.35.0` and `plugin-gradle 6.17.0` thanks to @STAR-ZERO.
@ibabel-chwy if you have a specific problem you should open a new issue and include the requested info (version, logs, etc)
This should be much improved in our latest `plugin-gradle 6.13.0` and `plugin-maven 2.30.0` thanks to - #1426 I'm going to close this again, but please reopen if it is still...
I think this will be solved by - #1524
> Is there any particular reason that Spotless Maven lacks parity with Spotless Gradle Nope, we just got PR's from Gradle users, that's all.
A PR for this would be very welcome. [`ForeignExe`](https://github.com/diffplug/spotless/blob/main/lib/src/main/java/com/diffplug/spotless/ForeignExe.java) might be the easiest way to implement it. It's okay if it only works on some platforms, so long as it...