jdaugherty commented on PR #15259: URL: https://github.com/apache/grails-core/pull/15259#issuecomment-3655799670
@codeconsole You're not presenting a technical argument here. We answered your questions: - There are more versions because we went to a mono repo. We decided to do this based on continuing to recommend the dependency management plugin & it's support for property based configuration. - As for the naming, this decision was to make it easy to configure based on the grails project name. We went with this in 7.0 so we can't change it now. The time to raise the name problem would have been prior to the 7.0 release. - As for a specific example, you seem to have not accepted the example I gave concerning fields. Could we have grouped these, yes. We decided against it to be more flexible. - As for adding a dependency via gradle instead, that isn't what's under question. These versions exist only because of the property support in dependency management. You don't even have to change code with the property support. An environment variable of `ORG_GRADLE_grails.fields.version=7.0.3` would override the version. Removing the properties, removes this support. I'm a -1 on this PR / code change until a technical reason can be given on why we should limit end apps flexibility & choice. -- 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]
