Cascade Build Fails - Missing Dependency
Gradle build fails with 'cannot find symbol' errors or 'unresolved dependency' when Cascade generated code that uses libraries not in your classpath. The generated code imports classes that don't exist in your project.
Cascade suggests library usage without automatically updating build configuration.
Error Messages You Might See
Common Causes
- Cascade generated code using library (e.g., Jooq, Testcontainers) not in build.gradle.kts
- Cascade imported classes from optional/transitive dependencies not explicitly declared
- Version mismatch: Cascade used API from newer library version than currently declared
- Cascade suggested removing dependency that other code still depends on
How to Fix It
Review Cascade-generated imports to identify missing libraries. Add dependencies to build.gradle.kts with appropriate versions. Ensure version alignment with existing dependencies. Run './gradlew compileKotlin' to verify build. Consider dependency management tools to detect conflicts.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
How do I find what library provides a class?
Search docs or use gradle dependencies task: ./gradlew dependencies | grep ClassName