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
Usually INFO and WARN messages from Spring will drive you up the wall and cause you to miss real problems. Except for the time when you have a Springish problem and the logs tell you exactly what beans are being created or if the local properties didn't get picked up.
There's got to be some way to change the log level at run time, thus we can add something to the centipede shell that accepts an option like
-springLogLevel WARN
so we can change the log level without having to patch the application source code.
Note another option is to have some way to set log4.properties in the local configuraton directory, since presumably people are going to want to be able to do that.
The text was updated successfully, but these errors were encountered:
Usually INFO and WARN messages from Spring will drive you up the wall and cause you to miss real problems. Except for the time when you have a Springish problem and the logs tell you exactly what beans are being created or if the local properties didn't get picked up.
There's got to be some way to change the log level at run time, thus we can add something to the centipede shell that accepts an option like
-springLogLevel WARN
so we can change the log level without having to patch the application source code.
Note another option is to have some way to set log4.properties in the local configuraton directory, since presumably people are going to want to be able to do that.
The text was updated successfully, but these errors were encountered: