nebula-plugins / nebula-plugins/nebula-archrules-plugin
Built-in support for per-sourceset configurable failure thresholds
@wakingrufus is already working on this.
Since May 26, 2026.
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 3
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
It would be nice if we could configure different failure thresholds per sourcesets. My use case would be permitting low-priority violations in tests. This is somewhat possible by manually wiring up an extra EnforceArchRulesTask (and excluding the test source-set from the standard logic), but this feels a bit hacky and like something that should be supported out of the box.
Introducing a mechanism for per-sourceset configuration would give far greater freedom and would blend naturally with Gradle's NamedDomainObjectCollection API.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.