mikepenz / AboutLibraries

AboutLibraries automatically collects all dependencies and licenses of any gradle project (Kotlin MultiPlatform), and provides easy to integrate UI components for Android and Compose-jb environments
http://mikepenz.github.io/AboutLibraries/
Apache License 2.0
3.66k stars 423 forks source link

Is there a way to silence logging? #872

Closed stkent closed 1 year ago

stkent commented 1 year ago

About this issue

When this plugin's prepareLibraryDefinitions task is run, we see lots of build output like:

> Task :app:prepareLibraryDefinitionsDebug
--> Retrieved POM for: com.atlassian.commonmark:commonmark from com.atlassian.commonmark:commonmark-parent:0.13.0
----> Retrieved POM for: com.atlassian.commonmark:commonmark from com.atlassian.pom:central-pom:5.0.13
------> Retrieved POM for: com.atlassian.commonmark:commonmark from com.atlassian.pom:base-pom:5.0.13
...
...
...

We like to minimize such output as it makes identifying newly-introduced warnings easier.

Is there a way to disable this output? (I scanned docs, but didn't see anything; apologies if I missed something!)

Details

Library version 10.6.2.

Checklist

mikepenz commented 1 year ago

Actually this looks like a bug as this uses a println statement instead of the LOGGER.info tag it's supposed to:

Would that solve the need? (E.g. have INFO log level for that item)

mikepenz commented 1 year ago

(Also to answer the pure question, there is no setting or option to fully turn off logs at this time)

stkent commented 1 year ago

Ah, yes, I suspect that using the logger and marking this output as informational would be perfect; I'm pretty sure we only log statements that are warnings or more severe!

mikepenz commented 1 year ago

This will be adjusted in the next update. Thanks for reporting!

stkent commented 1 year ago

Thank you for the quick response!