dokka version 0.9.13
kotlin version 1.1.0
gradle version 2.3
android studio 2.3
Error while syncing the project
Caused by: kotlin.KotlinNullPointerException
at org.jetbrains.dokka.gradle.DokkaAndroidPlugin.collectClasspath(mainAndroid.kt:45)
at org.jetbrains.dokka.gradle.DokkaAndroidPlugin.access$collectClasspath(mainAndroid.kt:15)
at org.jetbrains.dokka.gradle.DokkaAndroidPlugin$apply$2.execute(mainAndroid.kt:28)
at org.jetbrains.dokka.gradle.DokkaAndroidPlugin$apply$2.execute(mainAndroid.kt:15)
at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:93)
at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:82)
at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:44)
at org.gradle.internal.event.BroadcastDispatch.dispatch(BroadcastDispatch.java:79)
at org.gradle.internal.event.BroadcastDispatch.dispatch(BroadcastDispatch.java:30)
at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy16.afterEvaluate(Unknown Source)
at org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:82)
I'm having the same, and it also happens for Kotlin 1.0.6
Note that it doesn't happen for the android plugin 2.2.3.
Same here... I can't do a gradle sync...
Figured out here guys
The classpath in dependencies section was wrong.
It was pointing to a path that apparently doenst exist (or maybe just doesnt work with gradle 2.3)
So I had to change from
classpath "org.jetbrains.dokka:dokka-android-gradle-plugin:${dokka_version}"
into
classpath "org.jetbrains.dokka:dokka-gradle-plugin:${dokka_version}"
Everything OK here now. Please see more details in http://stackoverflow.com/questions/42929909/cant-build-project-with-android-studio-2-3-and-gradle
The solution posted by ggbc works, but we are just changing the dokka android plugin for the normal plugin (I'm guessing there is a good reason for having a different plugin for android). There is still something wrong with the android plugin which causes a KotlinNullPointerException.
I'm facing to a similar issue, when to you plan to release a version that fix this bug ? Do you have snapshots releases ?
We don't have snapshot releases, but you can easily build Dokka for
yourself ./gradlew publishToMavenLocal. Also, Dokka 0.9.14 will be
released after 1.1.2 Kotlin
On Wed, Apr 19, 2017 at 6:09 PM, Vincent Masselis notifications@github.com
wrote:
I'm facing to a similar issue, when to you plan to release a version that
fix this bug ? Do you have snapshots releases ?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Kotlin/dokka/issues/140#issuecomment-295303798, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB1HPPxU4z3DzdpgEVbhQjbuRBqhoU4iks5rxiO7gaJpZM4MR2Ux
.
--
Best regards,
Simon Ogorodnik
Junior Developer in Kotlin
JetBrains
http://www.jetbrains.com
The Drive to Develop
Thanks, I will try this way :)
All hitting this problem can try 0.9.14 EAP 3
version: 0.9.14-eap-3
Fixed in 0.9.14
Most helpful comment
We don't have snapshot releases, but you can easily build Dokka for
yourself
./gradlew publishToMavenLocal. Also, Dokka 0.9.14 will bereleased after 1.1.2 Kotlin
On Wed, Apr 19, 2017 at 6:09 PM, Vincent Masselis notifications@github.com
wrote:
--
Best regards,
Simon Ogorodnik
Junior Developer in Kotlin
JetBrains
http://www.jetbrains.com
The Drive to Develop