Migration to Gradle build and Idea's 2024 platform for plugins. #19
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
lachlanodonnell
changed the title
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.
Incorporated changes from #12
Updated to Gradle project, Intel plugin build style for 2023. Test build works under 2023.3.4 Intelij.
You should just need to add your certificate and keys to Gradle configuration to promote to JetBrains. See https://plugins.jetbrains.com/docs/intellij/developing-plugins.html for the latest Gradle configuration steps.
Note a lot of files were moved around to fit into a Gradle build shape. I used a generation of a standard plugin as an example then moved the files and added the new configs to setup.
Gradle assemble to build the plugin.
You can load the plugin from disk see build/distributions