codeconsole commented on PR #16165:
URL: https://github.com/apache/grails-core/pull/16165#issuecomment-5332487843
### Indy Whiplash?
I agree with this change, but I wonder if we should consider turning indy on
in the final release of 8? I think it is counter intuitive to go against
Groovy defaults and turn it opposite to normal compiler behavior. At the very
least we should consider not changing downstream plugin behavior and perhaps
enforce plugins indy true?
The following should be fully understood prior to 8.0.0:
1. Benchmark for an app with Grails compiled indy false, plugins false, and
app false. (Current 8 defaults)
2. Benchmark for an app with Grails compiled indy true, plugins false, and
app true.
3. Benchmark for an app with Grails compiled indy true, plugins true, and
app false. (Unknown?)
4. Benchmark for an app with Grails compiled indy true, plugins true, and
app true (default Groovy behavior)
Current state of Grails 8
indy OFF (29): `grails-cache, grails-fields, grails-geb, grails-mail,
grails-redis, grails-scaffolding,
grails-views-gson, grails-views-markup, grails-undertow/plugin,
grails-gsp/{plugin,grails-layout,grails-sitemesh3},
grails-data-hibernate5/{grails-plugin,dbmigration},
grails-data-hibernate7/{grails-plugin,dbmigration},
grails-data-mongodb/grails-plugin,
grails-data-graphql/plugin,` all 11 `grails-spring-security/*` plugin
modules.
indy ON (17, Groovy 5 default): `grails-core, grails-controllers,
grails-domain-class,
grails-url-mappings, grails-interceptors, grails-services,
grails-databinding, grails-converters,
grails-codecs, grails-mimetypes, grails-i18n, grails-datasource,
grails-micronaut,
grails-rest-transforms, grails-async/plugin, grails-events/plugin,
grails-data-neo4j/grails-plugin`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
