Minor Description
Currently, the dependency:analyze goal supports a parameter called failOnWarning which - when enabled - causes warnings to fail the build.
This is confusing, especially for new developers on a team who are often unable to locate the dependency problems causing the build to fail in the logs because they only look for "error" level messages.
To avoid such problems, I would suggest deprecating the failOnWarning parameter, and instead introduce a new parameter such as treatDependencyProblemsAs which could take as a default level "warning" and which users could alternatively set to "error".
I am setting this as a "major improvement" because in my experience, it causes significant confusion over and over again.
Attachments
Issue Links
- links to