Closed robertpatrick closed 2 years ago
Mojos provided by this plugin do not alter log settings, hence these warnings are logged directly by the oci-java-sdk operations. See for reference https://github.com/kordamp/oci-maven-plugin/blob/643bcf361bd31ede708a2813dd5d54962643041d/oci-maven-plugin/src/main/groovy/org/kordamp/maven/plugin/oci/mojos/object/DownloadObjectMojo.groovy#L57-L80
What could be done in the meantime is update your project settings so that logging for oci-java-sdk calls are filtered, using regular Maven means and Slf4j.
hmm...ok. I wonder why the SDK feels like these warrant log warnings...seems broken to me.
@aalmiray Apparently, the extra warnings can be disabled with a Java System Property. I feel like the plugin should disable these by default since the plugin user cannot really do anything with these warnings since they are not using the Java SDK directly. WDYT?
Agreed. Likely guardes by a boolean flag in case a user would like to see the hidden warnings.
@aalmiray The other option would be to show the warnings only when running a build in debug mode (i.e., mvn -X
)
Maven's debug mode is way too verbose for that. We can think of plugin verbosity vs. build verbosity.
Handling the system prop with a flag gives us the former, which could be forced to true
if -X
is given even if the flag was explicitly set to false
.
Handling it just with -X
gives us the latter option.
When using the latest
download-object
goal, my build output shows several warnings that are meaningless to me and seem to indicate possible issues with the mojo itself.If the user doesn't need to know (e.g., since there is no action that they can take to rectify the warning), they should either be suppressed or written at a lower log level.