chore: move grails-publish gradle plugin to its own project #14937
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jdaugherty
force-pushed
the
grailsPublishMove
branch
from
cd66711 to
d0c1d93
Compare
Contributor
Author
|
We cannot merge this until RC1 is released. |
jdaugherty
force-pushed
the
grailsPublishMove
branch
from
d0c1d93 to
1b8205a
Compare
jdaugherty
force-pushed
the
grailsPublishMove
branch
from
1b8205a to
ab496af
Compare
jamesfredley
approved these changes
Aug 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: plugin is moved here: https://github.com/apache/incubator-grails-gradle-publish
I still need to work with the ASF infrastructure to get the asf.yaml to correctly apply to incubator-grails-gradle-publish repo. Otherwise, this seems functional at this point.