Is there a way to silence logging?

[Stuart Kent]

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

• Searched for similar issues
• Checked out the sample application
• Read the README
• Checked out the CHANGELOG
• Read the MIGRATION GUIDE

[Mike Penz]

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

• AboutLibraries/plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/PomLoader.kt

  Line 42 in bebaf72

   println("${prefix}--> Retrieved POM for: $uniqueId from ${id.group}:${id.name}:${id.version}") 

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

[Mike Penz]

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

[Stuart Kent]

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!

[Mike Penz]

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

[Stuart Kent]

Thank you for the quick response!