-
Notifications
You must be signed in to change notification settings - Fork 40.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too much logging when building an OCI image with Maven #22674
Comments
When launched with
Changing that file isn't something Boot can do (although users could modify it themselves) so I'm not sure there's much we can do about this. |
Couldn’t we use the same shaded HTTP client? Or shade it again? I guess if not the best fix is to persuade the client to log all that craft at TRACE instead of DEBUG? |
It won't always be available as the code that uses the HTTP client isn't Maven-specific. It is used by the Gradle plugin as well.
I don't think that would help, unless we shaded it with Maven's
Either that, or to at least make it configurable. Looking at the HTTP Client code again, we might be able to provide our own equivalent of |
mvn spring-boot:build-image -X
logs every byte to and from the Docker daemon ...it's kind of too much. You get a lot of lines like this for example:The text was updated successfully, but these errors were encountered: