) and I would like to know if just running it in the linux runner is enough or I just run
on every single runner to detect code smells in all targets of all modules. I would like to avoid running specific
tasks because I am using reusable workflows in all projects and every project can have different targets and I want a modular workflow but not very complex one.
9 months ago
is a dump task. It only runs on src/main/java(kotlin) and src/test/java(kotlin). If you want it to run over other source sets you need to add them. (I'm on phone so please check the documentation to see how, I can't link it). And remember that you wouldn't be running the rules that need type solving.My recommendation is to add the task
to all your projects and configure it for each one in gradle. We need to refactor our gradle plugin. At the begging it was doing a very simple thing so the api was really simple but that api didn't evolve with the complexity of the project. But we would need to add lots of breaking changes to do that. It's a difficult topic. Any contribution to six this is more than appreciated as always.
9 months ago
I checked the config I did years ago and it looks like I am adding the entire project as sources and indicating the files detekt has to check