Fix published capability names #1
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GDI uses feature variants to publish the
runtimeandbasecomponents. It uses the automatically generated capability name for each of these; however, due to using a project name that does not line up with the published module name, this results in rather strange capability names, of the formatnet.neoforged:GroovyDSLImprover-runtimeinstead of the more sensible and expectednet.neoforged:groovydslimprover-runtime, to match the main published module. This PR fixes this, by changing the root project name to match the published module.Note that due to an IntelliJ quirk, if you are working on GDI in dev on Windows and apply this change, you may need to delete the
.ideafolder and re-import the project to get it to play nice.