You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.
It seems also that System.out.println are not working anymore in ConfigOptions after the switch to bti, so we should maybe use a logger to get the relevant output like for System.out.println("Spring Native operating in "+MODE+" mode");.
The text was updated successfully, but these errors were encountered:
All the existing verbose logging with spring.native.verbose was converted to proper Java logging. I'll change the remaining few sysouts under this bug. You can turn on verbose mode by using the standard maven -X option which turns on debug logging for a run (you will see everything that previously came out in verbose mode).
sdeleuze
changed the title
Fix ConfigOptions (and potentially other places) logging
Fix Maven plugin logging
Feb 19, 2021
I reopen it to review logging once #484 will be fixed since I can't see logs for example Spring Native operating in ... mode which was displayed without having to set spring.native.verbose. I think we should avoid requiring having to set -X, -e should be enough.
It seems also that
System.out.println
are not working anymore inConfigOptions
after the switch to bti, so we should maybe use a logger to get the relevant output like forSystem.out.println("Spring Native operating in "+MODE+" mode");
.The text was updated successfully, but these errors were encountered: