ISP 0.9

[WarningImHack3r]

The IntelliJ Platform Plugin Template 2.0 is now available and features the new IntelliJ Platform Gradle Plugin 2.0.

This upgrade requires (among others) the JDK 17, which requires the minimum-supported platform (IDE) version to be bumped to 2022.2. However, the IPGP 2.0 itself requires 2022.3 at least, so at the end of the day we need to increase the minimum version by one whole major version.

Upgrading to the JDK 17 is a major improvement on many fronts, being much better supported by the IntelliJ ecosystem overall and finally allowing getting rid of some deprecations.

2022.3 is the oldest possible version I can support with this combination of new versions. Dropping support for one major version is significant but reasonable enough to this day to keep the widest possible range of supported versions.
It also brings in common the supported range of versions for all my plugins, so it's easier for me to keep track of and it brings more consistency across my projects for the users.

Outcomes and sum-up

• The plugin now additionally depends on Webpack due to the newer version used for the Vue dependency. It shouldn't impact compatibility as it's already built-in for IDEs that support the Vue plugin.
• Support for 2021.3, 2022.1 & 2022.2 is dropped, 2022.3 is now the minimal supported version. Older versions can still use the 0.8.x versions of the plugin.
• Kotlin 2.0 is finally usable and upgraded
• The JDK 17 is the latest and best JDK to be on for IntelliJ products, upgrading from the old JDK 11
• The plugin size has increased from ~350KB to ~2.5MB due to the now hard dependency on kotlinx.serialization. This dependency would've been necessary in the future due to some features I'll need anyway. This new larger size is unchanged compared to the experimentations I made with this dependency back in 0.8.3.

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions