The newest versions of the dependencies can also be found here. But you have to change your dependency either way, so I recommend you go with kotlin-stdlib-jdk7, or if you plan on using Java 8, kotlin-stdlib-jdk8 1.3.0)Īlternatively, you can use the "plain" stdlib ( kotlin-stdlib) instead of the JDK-specific versions. Where $kotlinVersion is either a variable containing the version, or a hard-coded version (i.e. Implementation ":kotlin-stdlib-jdk8:$kotlin_version" These are the new valid dependencies as of Kotlin 1.3.0: implementation ":kotlin-stdlib-jdk7:$kotlin_version" You naturally have to do this if you're on 1.2.71 or lower, and you're upgrading to 1.3.0 or higher. For updating from older versions, the rest of the answer still applies I haven't checked whether it's been patched or not - if it has, that only fixes the creation of new projects. Therefore, you have to manually replace the dependencies with working ones until they fix this. They have probably not updated the project generators. kotlin-stdlib-jre is now no longer maintained as a separate dependency.īoth IntelliJ and Android Studio currently generate new projects using kotlin-stdlib-jre7 this likely is a bug. It's the same dependency as kotlin-stdlib-jre7 (except newer), but it was re-named to kotlin-stdlib-jdk. Using any of the deprecated versions (before it was removed) should also produce a warning in (at least) Android Studio and IntelliJ. The official deprecation notice can be found here. The deprecation note was kept until 1.2.71, which was the last version to release those artifacts. Kotlin-stdlib-jre was deprecated a while ago, and has since been removed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |