codeconsole commented on PR #15259: URL: https://github.com/apache/grails-core/pull/15259#issuecomment-3651779964
> It's not about which of these is better. Since Grails 7 applications are still generated with the Spring Dependency Management Grails Plugin, we support both pathways to override the grails artifact versions. This isn't a question of better. It's about proper bom design and using bom versions how they are intended. Versions are more there to specify versions for dependency groups, not individual submodules. There is no history of these 100+ versions existing. Why introduce them now? It's variable overkill. **_This looks more like a bug than a feature._** The correct approach would either be: 1. remove them completely or 2. create the appropriate groups (which is how historically it was done). Please explain what the expected behavior is in it's current design for: ``` grails.async.gpars.version=7.1.0-SNAPSHOT ``` will this also update grails async or just `grails.async.gpars`? if so, is the correct property name `grails.async`? Is this introduction of a 130 individual versions documented anywhere with usage instructions? -- 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]
