autonomousapps / autonomousapps/dependency-analysis-gradle-plugin
`onAny` does not cover `onDuplicateClassWarnings`
- Dominant language
- Kotlin
- Stars
- 2.2k
- Forks
- 158
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 46
Description
**Plugin version**
3.5.1 / 3.5.2-SNAPSHOT
**Gradle version**
9.2.1
**JDK version**
25
**Describe the bug**
I have `onAny { severity("fail") }` and got a duplicate class warning,
but the build did not fail. It only failed when I additionally specified
`onDuplicateClassWarnings { severity("fail") }`.
**Expected behavior**
`onAny` covering any issue
Contributor guide
Research direction
Start by reproducing the configuration with `onAny { severity("fail") }` and a duplicate class warning, then compare it with `onDuplicateClassWarnings { severity("fail") }`. Trace the `onAny` and `onDuplicateClassWarnings` entry points to determine why their severity handling differs. Done means `onAny` alone causes the duplicate class warning to fail the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100