[logging] Re-use 'verbose' to reduce logging output during runs #319
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.
I did look around and did not see any reports of wanting this data entirely hidden. This PR doesn't solve needs completely and probably needs another field to handle this as I'm mixing its usage with verbose. Maybe something with logging level here might do it.
Currently logging on this plugin is mostly in 'info' mode making it incredibility chatty with zero value in the data posted. This becomes worse during multi module builds that is aggregated and constantly replacing attached data. This PR won't solve all instances but will make a good attempt at reducing the output.
After reuse of 'verbose' here, when false which is default and may require some other way to achieve this would result in this.
I'd love to get that other warning to go away too but that is in cyclonedx and doesn't seem it can be hidden. How might we hid that too?
By default, normal plugin run gets this
Because I reused 'verbose' here as it made sense to do, turning that on would get the following.
I can see using a separate flag but wanted to get feedback first. Also suggestions on how to squash warning shown above as well as when multi module build and it states it already seen the creation and creates a new one to attach (replaces), how might that be squashed too?
Ideally I would want to run this without any data output at all since no data it outputs IMHO is something I want to see outside of debug run since its value at best is redundant. Of course it creates those files, that was the point, of course they are in target, again the point.