Open ZacSweers opened 4 years ago
Any thoughts?
Hm, personally I would not add specific source sets tasks to verification group - they will just pollute it.
Meta tasks (trigger all related source tasks) are in the verification group already. Could you explain me what you try to accomplish?
And maybe @JLLeitschuh has another opinion on it.
Could we put them in a ktlint group then?
Gradle doesn't support marking a task as "private". However, gradle tasks will only show a task if it either has task.group set, or no other task depends on it.
Actually we probably could set verification group on all tasks :thinking: Source Set tasks should be hidden as meta tasks depend on them. Could you create a PR?
What's the use case here again? Sorry.
To group them appropriately rather than all get dumped in "other"
From what I've seen, this plugin can end up generating quite a few tasks. Especially when you have the cross compilation Kotlin plugins applied. I'm concerned that a change like this adds little value and will just result in information overload in the output of :tasks
.
There's also the argument that many of the tasks that we generate are 'internal' and should only be executed in aggregate. Maybe I'm wrong.
When you add the 'group' it usually indicates to the user that we're fine that you explicitly invoke those specific sub-tasks instead of running the aggregator tasks. I don't know if that's the kind of behaviour we actually want to be encouraging.
Thoughts?
Currently tasks are group-less, which means they go on to a "other" catch-all. Would be nice if these could go in the verification group. Happy to send a PR.