If both ksp and kapt plugins are available, both also create bean definitions

[braeluca]

Expected Behavior

If both ksp and kapt plugins are available, only one should be used.

Actual Behaviour

If both ksp and kapt plugins are available, both also create bean definitions, which is inefficient. It also leads to and exception when building the jar:

Execution failed for task ':runnerJar'.
Entry org/example/$ExampleController$Definition$Reference.class is a duplicate but no duplicate handling strategy has been set. Please refer to https://docs.gradle.org/8.2/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:duplicatesStrategy for details.

However this can be resolved by specifying a duplicate strategy, but it is still inefficient. Sometimes kapt is also needed for other annotation processors.

Steps To Reproduce

1. Create application with micronaut launch: mn create-app --build=gradle_kotlin --jdk=17 --lang=kotlin --test=junit com.example.demo
2. Create any Bean or Controller
3. Add kapt plugin to build.gradle.kts
4. Run the assemble task

Environment Information

• Operating System: macos 13.4.1 arm
• JDK 17.0.6

Example Application

https://github.com/braeluca/micronaut-kapt-ksp-demo

Version

4.0.3

[sdelamo]

We don't support both KAPT and KSP at the same time.

[sdelamo]

why do you want to use KAPT and KSP simultaneously?

[braeluca]

Some other annotation processor does not support ksp and probably never will and therefore i need to apply also the kapt plugin to use these.

[graemerocher]

If KSP is present then the inject-java module shouldn't be added to the kapt scope

[graemerocher]

check needs to be added here

micronaut-gradle-plugin/minimal-plugin/src/main/java/io/micronaut/gradle/MicronautKotlinSupport.java

Line 110 in 33d6859

configureKotlinCompilerPlugin(project, KAPT_CONFIGURATIONS, "kapt", PluginsHelper.ANNOTATION_PROCESSOR_MODULES);

[melix]

The issue is that we cannot know when the kapt or ksp plugins are applied. So even if we add a check, it can fail. There's more going on than just the annotation processor being added too.

[braeluca]

But correct me if i am wrong: To apply the dependencies for kapt or ksp scope, it must know, that kapt or ksp are added, right?

An alternative could be to disable kapt in the micronaut plugin via a config.

[melix]

Yes, we can do something when the KSP plugin is applied, or when the kapt plugin is applied. That's what we do. The thing is that we do it "twice" when both are applied. Disabling via configuration could be used too, but it's not that easy either because the flag could be set after the configuration was applied...