What problem does it solve?
Upgrading a Kotlin project from Exposed 0.61.0 to Exposed 1.0 requires dozens of package renames, JDBC module moves, SqlExpressionBuilder import rewrites, and build-file dependency changes. Doing this by hand across a large codebase is error-prone and tedious, and some API changes cannot be automated safely at all.
Core Features & Use Cases
- Automated package renames: Rewrites old
org.jetbrains.exposed.sql.* and org.jetbrains.exposed.dao.* imports to the new org.jetbrains.exposed.v1.* namespace, including JDBC-conditional moves and SqlExpressionBuilder lambda imports.
- Build-file updates: Bumps Exposed coordinates to 1.0.0 in Gradle Kotlin/Groovy DSL, version catalogs, and Maven pom.xml, splits
exposed-migration, and adds exposed-jdbc when needed.
- Manual-review reporting: Detects 18 categories of changes that require human judgment (custom Transaction extensions, transaction() signature changes, removed APIs) and produces a structured summary with file:line references and migration-guide links.
- Use Case: You have a Spring Boot service on Exposed 0.61.0 with 200 Kotlin files. Run this Skill to apply all mechanical renames, update build.gradle.kts, and receive a checklist of the 12 items that need manual fixes.
Quick Start
Migrate my project from Exposed 0.61.0 to Exposed 1.0 and show me what needs manual review.