Codegen fails to detect language if Kotlin plugin is defined after codegen plugin
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 217
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Code generation fails to detect Kotlin language if the Kotlin plugin is defined after the dgs.codegen plugin.
Doesn't work:
plugins {
id("com.netflix.dgs.codegen") version "4.4.3"
kotlin("jvm") version "1.4.31"
}
Works:
plugins {
kotlin("jvm") version "1.4.31"
id("com.netflix.dgs.codegen") version "4.4.3"
}
Symptoms
- Codegen would generate Java classes instead of Kotlin
- More importantly, the codegen task would depend on the Java compile task and thus would not be executed automatically on a Kotlin project
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the two Kotlin Gradle plugin orderings shown in the report, then inspect how the codegen plugin detects Kotlin and wires its task dependencies. Done means both orderings generate Kotlin classes and make code generation run automatically in a Kotlin project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100