You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will include a number of breaking changes. We will document the changes and migration path and if time allows create an openrewrite script.
The groupid changes are required by the Apache Software Foundation at some point and the decision was made to go ahead and complete it for Grails 7 release, since the Grails 7 release already has a long list of breaking changes. The artifactid changes have been discussed a number of times and the goals are standardization, especially for plugins, and for the resulting jar filename to clearly indicate that this is Grails and if it is a plugin. The repackage is not required by ASF, but will allow companies to enforce security rules for packages.
groupid changes
org.grails -> org.apache.grails
org.grails.plugins -> org.apache.grails.plugins and move plugins in org.grails (we have plugins in two locations now and need to consolidate)
Plugins not moving to Apache:
After these steps are completed, Grails plugins which are not included in the core set of plugins migrating to Apache that live in https://github.com/gpc/, https://github.com/grails-plugins and other historical locations will continue to use org.grails.plugins group and org.grails.* package as desired.
The text was updated successfully, but these errors were encountered:
Groovy still has a mix of packages and we should make sure we understand why.
org.apache.groovy.*
groovy.*
org.codehaus.groovy.*
jamesfredley
changed the title
Apache migration: groupid and artifactid updates and repackage
Apache migration: maven groupid and artifactid updates and source code repackage
Feb 11, 2025
Issue description
Table: https://github.com/jdaugherty/grails-core/blob/renameProposal/RENAME.md
This will include a number of breaking changes. We will document the changes and migration path and if time allows create an openrewrite script.
The groupid changes are required by the Apache Software Foundation at some point and the decision was made to go ahead and complete it for Grails 7 release, since the Grails 7 release already has a long list of breaking changes. The artifactid changes have been discussed a number of times and the goals are standardization, especially for plugins, and for the resulting jar filename to clearly indicate that this is Grails and if it is a plugin. The repackage is not required by ASF, but will allow companies to enforce security rules for packages.
groupid changes
artifactid changes
grails-plugin-
repackage
org.grails.* -> org.apache.grails.*
grails.* -> org.apache.grails.internal.* ?????
Plugins not moving to Apache:
After these steps are completed, Grails plugins which are not included in the core set of plugins migrating to Apache that live in https://github.com/gpc/, https://github.com/grails-plugins and other historical locations will continue to use
org.grails.plugins
group andorg.grails.*
package as desired.The text was updated successfully, but these errors were encountered: