Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024.3 support - add com.intellij.modules.json dependency #456

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

asaarilahti
Copy link
Member

#455

PluginVerifier does not flag the issue, so unclear if this is enough. If it isn't, the plugin needs to be added to the plugins list in build.gradle.kts. This means that either the minimum supported Idea version needs to be bumped to 2024.3 or that multiple versions targeting different Idea versions need to be published.

@asaarilahti asaarilahti added this to the 1.5.0 milestone Nov 13, 2024
@zalando zalando deleted a comment from zalando-compr-opensource bot Nov 13, 2024

This comment was marked as outdated.

<depends>com.intellij.modules.lang</depends>
<depends>com.intellij.modules.json</depends> <!-- Bundled plugin starting from 2024.3 -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So if the previous versions of IntellIj don't have this, will it still work with older versions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I understand, it has been a module and in 2024.3 it was migrated to a (bundled) plugin. So, older versions have it and the declaration for the dependency was just missing.
However, it's not clear if this will be enough, or if we need to also add a plugin dependency. The challenge there is that the json plugin is only available for 2024.3.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for explanation. But how would we then find out? Just merging this PR and see what happens?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally yes. We can do a release to the beta channel.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So what is then preventing us to move this PR from draft to ready for review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants