[
https://issues.apache.org/jira/browse/MNG-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-6065.
-------------------------------
Fix Version/s: (was: 3.7.0-candidate)
3.7.0
Assignee: Robert Scholte
Resolution: Fixed
Fixed in
[d2510749d8c6677e8aa5db84f15a6e0075bab840|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=d2510749d8c6677e8aa5db84f15a6e0075bab840]
and
[22fad782b68368653e67d69d5e6b097603f050bd|https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=22fad782b68368653e67d69d5e6b097603f050bd]
Thanks for the patches!
> Creating option --fail-on-severity / -fos to support errorless or warningless
> builds
> ------------------------------------------------------------------------------------
>
> Key: MNG-6065
> URL: https://issues.apache.org/jira/browse/MNG-6065
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.5.0
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Labels: infosupport
> Fix For: 3.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I've been thinking the option {{--fail-level}} / {{-fl}} which is {{error}}
> by default, but could be changed to {{warning}}/{{warn}}. We've had similar
> request and they make sense: one should be able to execute a build without
> any warnings.
> I did an attempt to hook into the Logger to but that seems very tricky. The
> other option is to have this level available in the API, so Maven core and
> plugins can verify it for themselves and decide to throw an Exception. It is
> a simple implementation, but now every component is responsible for checking
> it, not really my preferred solution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
