Drop support for 2022.1

[PawelLipski]

As of May 23rd, 2022, it looks that from 2022.2 on, IntelliJs will run on JDK 17 🎉

Dropping support for 2022.1 might then include switching to Java 17 in code, including:

• triple-quote (Scala/Groovy-style) strings
• switch expressions (no more vavr Match)
• records (no more lombok @Data)
• pattern matching for instanceof

and others, see https://dzone.com/articles/whats-new-between-java-11-and-java-17

[KotlinIsland]

Why not rewrite the project in Kotlin 😳

[PawelLipski]

Coz b u d g e t 😅

[KotlinIsland]

Well Kotlin is designed to be very incrementally adoptable, and it already offers the three features mentioned in the OP (and many more). The project already has Kotlin set up, If you are going to write new code, why not write it in Kotlin 😃 .

[PawelLipski]

Certain parts are already written in Kotlin indeed! Like certain dialogs under frontend/actions/

[KotlinIsland]

Any thoughts on using Kotlin Compose (and here) or the Kotlin UI DSL or for the UI?

[mkondratek]

I think it's an excellent idea to have more Kotlin in the codebase 🚀 Kotlin is better in many ways (mentioned and not mentioned here).

In particular, #791 - using Kotlin DSL for that is the only option IMHO 👍

@KotlinIsland if you want to help us with the adoption of Kotlin feel free to take some issues 🛠️
We are open to contributions 🙂 you can start from that slide in auto-complete thing

[PawelLipski]

One thing to check before migration to Java 17: #1584 => EDIT: okay, Android Studio also migrated to Java 17 as of 2022.2