-
-
Notifications
You must be signed in to change notification settings - Fork 951
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
Removing deprecated logback.groovy
logics and docs from Grails 7
#13927
Comments
Dynamic groovy configuration of logging via groovy is an extremely useful feature to us. I really hope it can continue to be easy to enable in grails 7, via, say https://virtualdogbert.github.io/logback-groovy-config/ At the very least, would be worth getting the take of VirtualDogbert(Tucker) on this, given how much time he has put in on this plugin, including how to use it in grails |
@gsartori this is somewhat related to grails/grails-doc#907. I lean towards updating the documentation to reflect the options in grails-doc and if needed here in grails-core. grails/grails-doc#907 is default for Grails 7 and the "Logback Logging with Groovy config" is an optional feature powered by https://virtualdogbert.github.io/logback-groovy-config/ |
What about the security implications of using |
I don't agree with the supposed security reasons that the logback project gave. They amounted to: groovy is dynamic, and you can do dynamic things with it, thus it could be used wrongly. With this reasoning, The added protections that the logback-groovy-config project gives should make it much harder to accidentally create a vulnerability too. We should continue to tell people how to configure it, but we shouldn't try to disable it or hide it. The default is to create a logback.xml and if you want to use only xml, you have that choice. |
Okay, I guess we can close this issue than. I think this discussion was useful nontheless at lest to keep track of the decision |
I was trying the following on a Grails 7 app: It doesn't work, it looks like the https://virtualdogbert.github.io/logback-groovy-config/ plugin is not compatible with Grails 7 because of the Groovy version it uses.
I don't know, I keep thinking that "less is more". I am not so convinced that keeping the I think we should either:
Staying in the middle is the best way to be inconsistent. And inconsistent projects are not those projects people want to choose or invest in. |
The framework does not support Documentation does need to be updated in a few locations to remove references to That non-default, optional plugin adds Groovy support to logback, so only users that want/need it can have it. But it's not there unless they add the plugin. The Groovy compatibility stuff can be handled in a number of ways, the Plugin is updated to Groovy 4, exclude the Groovy dependencies from the plugin when declared in dependencies {} or use Gradle dependency substitution to change the version from 3 to 4. |
I've updated the documentation: grails/grails-doc#936 |
Feature description
I'm proposing we remove the deprecated
logback.groovy
feature.It's been deprecated for three years now (since 2021-12-16) because of security issues and given the impact of the Grails 7 release I believe is a good timing to do some cleanups.
See: https://stackoverflow.com/questions/74445304/is-there-a-reason-why-logback-groovy-is-discarded-in-1-2-9
If that's ok I can work on it
The text was updated successfully, but these errors were encountered: