Log issues at ERROR level with ignoreFailures = false#1038
Open
jonasfa wants to merge 4 commits intoJLLeitschuh:mainfrom
Open
Log issues at ERROR level with ignoreFailures = false#1038jonasfa wants to merge 4 commits intoJLLeitschuh:mainfrom
ERROR level with ignoreFailures = false#1038jonasfa wants to merge 4 commits intoJLLeitschuh:mainfrom
Conversation
ERROR level instead of WARNING
Collaborator
|
I think you make a valid point here, but I think the use case is a little more complex. I think it really should log at warn is |
Author
|
@wakingrufus thanks for the input! I've updated the tests and implementation, and rebased. |
ERROR level instead of WARNINGERROR level with ignoreFailures=false
ERROR level with ignoreFailures=falseERROR level with ignoreFailures = false
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The issues causing a build failure are most relevant, even when the user requests a quiet output.
Gradle plugins that print the issues causing a failure at
ERRORlevel include:Android Gradle Plugin (lint)
io.gitlab.arturbosch.detekt
Current ktlint-gradle behavior
Currently, when Gradle is invoked with log level
QUIET, the issues causing a failure are missing from ktlint-gradle's output.Proposed behavior
ktlint-gradle should log issues at
ERRORlevel instead.This PR results in the following output change when Gradle is invoked with
--quiet:The output remains unchanged when any other log level is requested, or when no log level is requested (default).
Reference
https://docs.gradle.org/current/userguide/logging.html#logLevels