-
Notifications
You must be signed in to change notification settings - Fork 22
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
Upgrade to Intellij platform gradle plugin 2.0 #70
Conversation
1. adds GitHub actions changes 2. add plugin info in the build.gradle.kts 3. adds IC-233 source folder
Co-authored-by: Khushboo <[email protected]>
…ion#63) * Support IntelliJ 2024.1, and update release to v2.6.0 * Add IC-2024.1 to release.yml product list
* Changes SExpression children to use `SEXPRESSION_ATOM` instead of `VALUE` * Adds changes in `IonSExpressionBlock` to consider `SEXPRESSION_ATOM` as children as per BNF grammar * Adds changes in `IonCodeBlockSpacing` to correctly consider `SEXPRESSION_ATOM` as children as per BNF grammar * Adds changes in tests for usign correct node names * Adds changes for PR workflow to run Gradle Build task
1. Adds IC-242 source folder 2. Upgrade gradle. Intellij 2024+ (242+) needs gradle 8.2+ 3. Add plugin info in the build.gradle.kts 4. Adds GitHub actions changes
Thanks for your contribution! |
Sure, will do. Also let me know once you update Github action |
I've fixed the GitHub Action and merged the fix into your PR. Now the workflow is failing because of this error, which looks related to the Intellij platform gradle plugin update.
|
I have updated the PR to include only changes related to Intellij platform gradle plugin 2.0 upgrade |
The workflows are failing becuase Do you suggest to change the code to hard code the prefix = |
I don't have a preference either way, as long as it works. If/when we support other IntelliJ IDEs, we can revisit if we need to. |
Pushed a commit to fix the workflow failure, please trigger it as I am unable to trigger |
Now it is failing due to a compilation error which I guess is because the minimal supported intellij platform is
Question: Can we remove build for |
Yes. In fact, if it makes things easier, we can drop support for all of the 2023 versions as well. People who are still using older versions of IntelliJ can continue to use older versions of the plugin. |
…d version is 2022.3 by new intellij platform plugin
Removed support for |
I'm not sure of the root cause for this failure. If I had to guess, I'd say there's a misconfiguration of the classpath or there was some breaking API change from IntelliJ. Were you able to successfully run If you're able to figure it out, that's great, but if not, I'll also try to look into this more sometime in the next few days. It seems like every fix is uncovering another issue, and I know that can be pretty discouraging sometimes. Thanks for being persistent and sticking with it this far! |
As you may have noticed, I figured out the dependency issue, and I've merged the PR. Thanks for all your work on this! |
Thanks for fixing it! Answering to your question: Both ./gradlew buildPlugin and ./gradlew verifyPlugin ran successfully locally in my machine. I wonder why |
Upgrade to Intellij platform gradle plugin 2.0
2.7.1
2022.2
in favour of2024.2
as the minimal supported version by new intellij platform plugin is2022.3
References
Testing
./gradlew buildPlugin
./gradlew verifyPlugin
2024.1
version