Investigation of the bug with plugin order application. #385
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See the issue: #384
The order in which atomicfu-gradle-plugin and kotlin-gradle-plugin are added to the classpath defines actual dependencies found on the classpath.
Also, the description of this problem for coroutines: Kotlin/kotlinx.coroutines#3984
Started to fail after these change in atomicfu #377 : atomicfu compiler plugin should be manually added to the classpath by the user.
To reproduce:
./gradlew clean publishToMavenLocal
cd integration-testing/examples/plugin-order-bug/
gradle clean build
It fails with the error:
The build is successful 🙃
What changes is the the Kotlin compiler classpath. When kotlin-gradle-plugin is applied first no
org.jetbrains.kotlinx-atomicfu-0.23.2-SNAPSHOT-commonMain-GuV53w.klib
is found, hence the compilation error is thrown.To check Kotlin compiler args, I ran the build with --debug and found
:compileCommonMainKotlinMetadata Kotlin compiler args: -classpath