James, Thank you for building a full table based on the thoughts captured in https://github.com/apache/grails-core/issues/14006 back in Feb. This looks really good.
My initial thoughts and opinions on the table: https://github.com/jdaugherty/grails-core/blob/renameProposal/RENAME.md org.apache.grails.gradle is excellent for grouping. I love this idea. groupids org.apache.grails.plugins and org.apache.grails.profiles end up with redundancy in the artifactid, but I prefer this groupid/artifactid grouping and redundancy over not having it. The artifactid containing grails-, grails-plugin-, grails-profile- or grails-gradle-plugin- is important so that the jar filename is clear and descriptive when pulled from maven central and you are viewing them in a fat jar/war or directory. There are a few that do not have one of these prefixes and I think a prefix should be added to the artifactid. grails-gradle-plugins is slightly confusing when grails-gradle-plugin-*'s exist. Maybe something like grails-gradle-plugin-core/base/main/common, same for grails-gradle-view-plugins grails-view-plugin- and grails-security-plugin-, should plugin come before view and security? I agree with grails-gradle-plugin, but am unsure on these two. The 2 artifactids that start with views- should start with grails-views- I think org.apache.grails.forge:grails-cli should be org.apache.grails.forge:grails-forge-cli. This may be a good time to rename grails-shell to grails-shell-cli also. The long artifactids, like, org.grails.grails-gsp.gradle.plugin, are the way Gradle Plugins can be published to a non-Gradle Plugin Portal, maven repository and still referenced by plugins { id } in build.gradle. They end up published, at least partially, in two locations to make the id work in Gradle. More details on that mechanism: https://github.com/apache/grails-gradle-plugin/issues/351#issuecomment-2537359841 . We have begun using "apply plugin" in most location due to the fact that plugins { id } is not working with snapshots, due to the problems listed in that issue. Can we standardize gorm-, grails-datastore-gorm-, grails-gorm-plugin- and grails-datastore- around grails-data- and grails-plugin-data- James On 2025/03/19 12:44:48 James Daugherty wrote: > Hi Everyone, > > Per previous meetings, we agreed to rename the maven coordinates as part of > transitioning to the ASF. During this renaming, we also set out several > requirements for being consistent with our group ids and artifact ids. > Since these renames are going to be referenced heavily by anyone upgrading > to the ASF packages, I am proposing we create a 'RENAME.md' markdown file > in the grails-core repository. We can then later include this file on the > website, grails docs, etc. > > My attempt at mapping the new group ids and artifacts ids are here: > https://github.com/apache/grails-core/blob/9ac56cac136f5228d783bda5671a49d433901ba5/RENAME.md > > > The PR to add this file to grails-core is here: > https://github.com/apache/grails-core/pull/14074/files > > Can people either comment on the PR or discuss here for the proposed > renames? > > Regards, > James >
