What is the difference between these two :thinking...
# gradle
g
What is the difference between these two 🤔 •
org.jetbrains.kotlin.plugin.allopen
◦ https://mvnrepository.com/artifact/org.jetbrains.kotlin.plugin.allopen •
org.jetbrains.kotlin:kotlin-allopen
â—¦ https://mvnrepository.com/artifact/org.jetbrains.kotlin/kotlin-allopen
🤔 2
s
Check their file contents and checksums to confirm, but in the past the Kotlin team will release something under one name, and change the name later. In order to maintain backwards compatibility, they continue to release it under the old name too. They are kind to do this. This appears to be them maintaining backwards compatibility for you. This seems to be the new naming strategy. I encourage you to use this one - https://mvnrepository.com/artifact/org.jetbrains.kotlin.plugin.allopen/org.jetbrains.kotlin.plugin.allopen.gradle.plugin
g
Thanks!
v
No, that's not at all correct. The second is the artifact that contains the actual Gradle plugin code. The first is the marker artifact with which a pure plugin id is resolved to some code. If you have in your build script
Copy code
plugins {
    id("org.jetbrains.kotlin.plugin.allopen") version "1.7.22"
}
this is translated to the marker artifact
org.jetbrains.kotlin.plugin.allopen:org.jetbrains.kotlin.plugin.allopen.gradle.plugin:1.7.22
by naming convention. The marker artifact then has no own jar, but just depends on the actual code artifact (which could contain multiple plugins each with its own marker artifact)
g
Oh -- ty @Vampire!
v
yw