[
https://issues.apache.org/jira/browse/MNG-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864030#comment-16864030
]
Robert Scholte commented on MNG-6065:
-------------------------------------
Yes, at least these 3 should be supported. I'm not sure if should use a
predefined set of let it depend on the actual logging framework. For instance:
some logging frameworks support fatal as well.
For now I would expect that a predefined set is easier to implement, so let's
start with that. Once people want more finegrained options, we could consider
it than.
> Creating opton --fail-level / -fl which is error by default, but could be
> changed to warning/warn.
> ---------------------------------------------------------------------------------------------------
>
> 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
> Priority: Major
> Labels: infosupport
> Fix For: needing-scrub-3.4.0-fallout
>
>
> 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
(v7.6.3#76005)
