kotlin-tooling-java-to-kotlin

Converting Java to Kotlin without breaking Spring or Hibernate requires preserving annotation target sites and behavior. This Skill applies framework-specific semantics for Spring, Hibernate, Jackson, Micronaut, and Quarkus during translation to ensure stable outputs.

Migrating Java source files to idiomatic Kotlin for large projects requires a disciplined 4-step methodology. This approach supports incremental updates, module-by-module conversions, and project-wide refactors while preserving signatures and framework semantics.

Java to Kotlin conversion does support testing and reactive frameworks like JUnit and RxJava. It also handles Dagger/Hilt, Guice, Retrofit, and Mockito, ensuring Kotlin-friendly idioms and explicit open constructors as needed.

Kotlin annotations may target the wrong site after converting from Java due to differing annotation application rules. Correct annotation site targets must be explicitly applied during translation to maintain framework compatibility and stable behavior.

You can use this Java to Kotlin migration approach for incremental updates instead of a full rewrite. It supports module-by-module conversions and project-wide refactors, outputting stable .kt files that preserve behavior.