You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2020/07/17 15:29:00 UTC
[jira] [Updated] (MDEP-602) Turn warnings into errors instead of
failOnWarning
[ https://issues.apache.org/jira/browse/MDEP-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold updated MDEP-602:
---------------------------------------
Labels: S2 (was: )
> Turn warnings into errors instead of failOnWarning
> --------------------------------------------------
>
> Key: MDEP-602
> URL: https://issues.apache.org/jira/browse/MDEP-602
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: analyze
> Affects Versions: 3.0.2
> Reporter: Richard Eckart de Castilho
> Priority: Minor
> Labels: S2
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)