We are also explicitly adding @Slf4j where we need logs so we can have auto completion with IntelliJ Community Edition.
Another plus is that the “log” usage is documented by the annotation. I have this idea we should define the “conventions” to help Grails be perceived less “of the elite” and more “of the people” to raise adoption. Having auto completion working out of the box from the IDE without the Grails plugin is one step on that direction (yes we should have an open source IDE plugin…) That would be my reason to document and promote the usage of the @Slf4j annotation. I personally also like cleaning up Grails 7 dependences if there is no need for them. Gianluca Sartori On Wed, 12 Mar 2025 at 18:06, Mattias Reichel <mattias.reic...@gmail.com> wrote: > In my Grails applications, I remove the grails-logging library and > explicitly annotate classes with @Slf4j where logging is needed. > > My question is: Is it worth maintaining a library whose sole purpose, as > far as I know, is to automatically add @Slf4j to all Grails artifact > classes? >
