-
Notifications
You must be signed in to change notification settings - Fork 92
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
Update the log4j.properties files #1950
Comments
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Jul 12, 2024
* Print the full class path with the line number this way the IDE can link the message to the corresponding class * Disable log related to the connection: it's useful only in certain situations and too verbose otherwise
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Jul 12, 2024
* Print the full class path with the line number this way the IDE can link the message to the corresponding class * Disable log related to the connection: it's useful only in certain situations and too verbose otherwise * Uniform all log configurations in the different modules
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Jul 12, 2024
* Print the full class path with the line number this way the IDE can link the message to the corresponding class * Disable log related to the connection: it's useful only in certain situations and too verbose otherwise * Uniform all log configurations in the different modules
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Jul 12, 2024
* Print the full class path with the line number: this way the IDE can link the message to the corresponding class * Disable log related to the connection: it's useful only in certain situations and too verbose otherwise * Uniform all log configurations in the different modules
DavideD
added a commit
that referenced
this issue
Jul 12, 2024
* Print the full class path with the line number: this way the IDE can link the message to the corresponding class * Disable log related to the connection: it's useful only in certain situations and too verbose otherwise * Uniform all log configurations in the different modules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: