Fix legacy not being able to access JetBrains annotations#275
Merged
Conversation
|
shartte
approved these changes
Jul 17, 2025
|
🚀 This PR has been released as ModDevGradle version |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
It turns out that the implicit
compilevariant of the mcp data was being used, instead of themcpApiElementsvariant that adds the dependencies from the JSON. As such we use the same workaround as was used for the forge dep: add a dummy capability to the implicit variants to prevent them from getting selected.This also fixes #272 for the same reason.