feat: move extra logging to info level #160
Open
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.
Currently the plugin prints out 5 separate log messages describing refs, configurations, versions, and describeTagFirstParent, plus a newline.
This is in addition to printing out the actual fully resolved version. The vast majority of the time this information is not valuable, but it gets printed even when running other gradle tasks (like compile!) in a project that uses this plugin.
This commit moves these messages to the info log level so they are not printed by default all the time, and instead only become visible if you add the --info (or higher) log level.
Example from my project's
compileJava
task before this change:Clearly this information is not relevant to users running the
compileJava
task.And after this change:
And here's what it looks like when you run the
version
task:And