[
https://issues.apache.org/jira/browse/MNG-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863832#comment-16863832
]
Robert Scholte commented on MNG-6065:
-------------------------------------
It could be any loglevel, but info, debug and trace don't make any sense. The
other option we need to add is {{off}}, which you could consider as the current
default option.
And no, --fail-level must always have an argument, but if you don't specify
this flag, it will fall back to the default.
We need to have a look at the impact of this. If it is too high (worse
performance), then we shouldn't have a default and just use the current
mechanism.
So yes: currently failing the build is caused be a thrown exception, totoally
unrelated to the logging that's been done.
> 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)
