Add for removal to previously deprecated methods and classes#15470
Add for removal to previously deprecated methods and classes#15470
Conversation
Add for removal and also to the adapter and the adapter bean.
Add for removal.
This is useful as it runs in the same context as setup() but only runs once. This gives you access to objects not yet initialized in setupSpec().
Update docs and usages to the preferred `updatable` property name. Cheap to keep backwards compatibility, so no urgent need to remove.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add since.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
Add for removal.
jdaugherty
left a comment
There was a problem hiding this comment.
This seems reasonable. It also reminded me of the GrailsDomainClass vs PersitentEntity change. Should we consider removing domainclass? I know it's a major change but in line with hibernate it may be worth it.
I looked at |
|
@matrei both James and I agree on this but this PR is a draft. Can we move forward with this? |
This will make it easier to remove these in 8 or later.