We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Logback dropped support for grooovy configuration since 1.2.9.
Details info could be found in news for Dec 16, 2021 http://logback.qos.ch/news.html
There are a lot of mentions of this way for configuring logs in documentation and probably also in templates. Better to remove them.
Current result - application will fail to run (including integration tests) if logback is updated to 1.2.9
The text was updated successfully, but these errors were encountered:
Just to mention, update to Logback 1.2.9 is desirable since the recent CVE-2021-42550 affecting Logback 1.2.7 and older.
Sorry, something went wrong.
There were some discussions from Logback JIRA , grails framework nead to support backward compatibility.
Spring Boot 2.6.2 use Logback 1.2.9 now, so if Grails 5.1.2 upgrade to Spring Boot 2.6.2, it would cause some errors with logback.
Logback still supports programmatic configuration. Grails could:
com.qos.logback.classic.spi.Configurator
Is it just me, or is arbitrary code execution when you have access to the server's files, a non-issue?
No branches or pull requests
Logback dropped support for grooovy configuration since 1.2.9.
Details info could be found in news for Dec 16, 2021 http://logback.qos.ch/news.html
There are a lot of mentions of this way for configuring logs in documentation and probably also in templates. Better to remove them.
Current result - application will fail to run (including integration tests) if logback is updated to 1.2.9
The text was updated successfully, but these errors were encountered: