Use SourceSet in task names and reports files names.

[Tapchicoma]

After reflecting on last discussion in #153, I think that it is better to rename check/format tasks, so they include SourceSet in their name (generated reports names are adjusted as well).

This better reflects on what exactly sources task are working.

Related to #170

[JLLeitschuh]

This is an API breaking change is it not?

[Tapchicoma]

Kind of, though I don't think it is something very breaking:

• hidden tasks names changed from ktlintMainCheck to ktlintMainSourceSetCheck
• generated report names also changed accordingly

Meta tasks names stays the same.

[JLLeitschuh]

Yea, I still think we have to mark this as a breaking change, unfortunately.

[Tapchicoma]

Fine for me, we can do next release as 7.0.0. I am also considering to use Gradle 5.0 as minimal supported version.

[JLLeitschuh]

Sure, that would make sense.

[Tapchicoma]

@JLLeitschuh updated changes in CHANGELOG.md to have better phrasing and include breaking word

[tasomaniac]

It is so nice with Kotlin to be able to do this.

[tasomaniac]

I don't think there is such think as hidden tasks. All the tasks created are public. If they are not put into a group then they are less visible. Since these tasks are grouped in verification, I would say they are pretty public. 👍 for making it a breaking change.

[tasomaniac]

Would be great to have an example for Android. Something like below?

Example: In an Android project with foo flavor, ktlintFooDebugSourceSetCheck task will check the foo sourceSet (not main). ktlintFooDebugCheck meta task will check all the sourceSets for fooDebug build variant.

[Tapchicoma]

I will add this explanation to the next PR that adds such variant meta tasks, as it, imho, belongs there.

[tasomaniac]

Agreed 👍

[JLLeitschuh]

I don't have any additional feedback to offer. If you want to add an example like @tasomaniac suggested, go for it. Otherwise, I'm happy to let this in as is.