-
-
Notifications
You must be signed in to change notification settings - Fork 72
BootStrap init closure servletContext cleanup #957
Conversation
matrei
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, why are we injecting something that is not used?
Why are we even having a BootStrap class that does nothing?
|
We generate a bootstrap class by default. Maybe we should do what spring does and just combine bootstrap with he application class @matrei |
|
I've used the code as generated by the (newly refactored) Grails 7 BootStrap template. The injection is not used but it documents how to inject the ServletContext. True it may be removed in those BootStraps that actually contain code. |
@jdaugherty I think it's fine when we generate starter apps. But why keep it around if it is not used? The |
|
My only concern with removing classes that we generate is we diverge from how people are likely setting up grails apps. There are a lot of ASTs and injecting of functionality in grails. This has the potential to not be testing what people are using. I'd leave bootstrap so we stay true to what most grails apps look like - even if it is empty. |
|
@matrei per discussion, I've taken this discussion to a ticket longer term: apache/grails-core#14021 |
|
@gsartori please feel free to merge this in the mean time. |
|
I cannot see the |
See: apache/grails-forge#507 (review)