Proposal: replace `check` and `apply` with a single task with a CLI flag

Instead of having spotlessCheck and spotlessApply, we could instead just have spotless, which could do the same thing as spotlessCheck. In place of spotlessApply, the user would instead run gradlew spotless --apply.

This might mesh better with the incremental build model being implemented in #31.

[nedtwigg]

I did my profiling using DurianDebug, especially StepProfiler. It’s helpful for “println()” profiling. The downside is there’s no way to do it without hacking up the code. I’ll push up a profile branch that shows one way to do it. Great cleanup in recent commit to 3.x btw 👍

[oehme]

Yes and that field would have to be static (as tasks are recreated on each build), which is exactly what I proposed above.