https://kotlinlang.org logo
#dokka
Title
# dokka
i

Ignat Beresnev

07/13/2022, 12:22 PM
Dokka 1.7.10 has been released 🥳 This is a bugfix release that addresses several blockers and regressions. Full changelog: Gradle plugin • Do not expose Kotlin stdlib in plugin dependencies, this should fix errors like Module was compiled with an incompatible version of Kotlin when using Dokka. Thanks to @mbonnin Java sources • Fixed build failure caused by having configured source links for Java code • Fixed several exotic problems that led to build failures, all related to using annotation in Java sources • Fixed IntelliJ platform
WARN: Attempt to load key
messages that appeared when analyzing Java sources Release notes on GH: https://github.com/Kotlin/dokka/releases/tag/v1.7.10
K 6
👍🏾 1
👍 1
m

mbonnin

07/14/2022, 3:21 PM
Heads up looks like the pom file on
gradlePluginPortal()
doesn't contain the excludes for some reason
i

Ignat Beresnev

07/14/2022, 3:27 PM
🤔 publication to Gradle plugin portal and maven central was from the same branch and even the same CI build, so that's strange... I did test 1.7.10 on one of the projects that experienced this issue, and everything was fine, although now I'm not sure where from it got Dokka's artifacts - m2 or plugin portal...
m

mbonnin

07/14/2022, 3:27 PM
Yea, this is super weird
For the record, this is the diff I get:
Copy code
$ diff -s dokka-gradle-plugin-1.7.10.pom dokka-gradle-plugin-1.7.10.pom.1 
1,2c1,7
< <?xml version="1.0" encoding="UTF-8" standalone="no"?>
< <project xmlns:xsi="<http://www.w3.org/2001/XMLSchema-instance>" xsi:schemaLocation="<http://maven.apache.org/POM/4.0.0> <http://maven.apache.org/xsd/maven-4.0.0.xsd>" xmlns="<http://maven.apache.org/POM/4.0.0>">
---
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="<http://maven.apache.org/POM/4.0.0>" xsi:schemaLocation="<http://maven.apache.org/POM/4.0.0> <https://maven.apache.org/xsd/maven-4.0.0.xsd>" xmlns:xsi="<http://www.w3.org/2001/XMLSchema-instance>">
>   <!-- This module was also published with a richer model, Gradle metadata,  -->
>   <!-- which should be used instead. Do not delete the following line which  -->
>   <!-- is to indicate to Gradle or any Gradle module metadata file consumer  -->
>   <!-- that they should prefer consuming it instead. -->
>   <!-- do_not_remove: published-with-gradle-metadata -->
6a12,33
>   <name>Dokka gradle-plugin</name>
>   <description>Dokka is a documentation engine for Kotlin and Java, performing the same function as Javadoc for Java</description>
>   <url><https://github.com/Kotlin/dokka></url>
>   <licenses>
>     <license>
>       <name>The Apache Software License, Version 2.0</name>
>       <url><http://www.apache.org/licenses/LICENSE-2.0.txt></url>
>       <distribution>repo</distribution>
>     </license>
>   </licenses>
>   <developers>
>     <developer>
>       <id>JetBrains</id>
>       <name>JetBrains Team</name>
>       <organization>JetBrains</organization>
>       <organizationUrl><http://www.jetbrains.com></organizationUrl>
>     </developer>
>   </developers>
>   <scm>
>     <connection>scm:git:<git://github.com/Kotlin/dokka.git></connection>
>     <url><https://github.com/Kotlin/dokka/tree/master></url>
>   </scm>
13,14c40,57
<       <type>jar</type>
<       <optional>false</optional>
---
>       <exclusions>
>         <exclusion>
>           <artifactId>kotlin-stdlib</artifactId>
>           <groupId>org.jetbrains.kotlin</groupId>
>         </exclusion>
>         <exclusion>
>           <artifactId>kotlin-stdlib-jdk7</artifactId>
>           <groupId>org.jetbrains.kotlin</groupId>
>         </exclusion>
>         <exclusion>
>           <artifactId>kotlin-stdlib-jdk8</artifactId>
>           <groupId>org.jetbrains.kotlin</groupId>
>         </exclusion>
>         <exclusion>
>           <artifactId>kotlin-stdlib-common</artifactId>
>           <groupId>org.jetbrains.kotlin</groupId>
>         </exclusion>
>       </exclusions>
It's also weird that the pom file is even used 🤔
(given that there is a more detailed .module file...)
i

Ignat Beresnev

07/14/2022, 3:33 PM
How did you notice it by the way?
m

mbonnin

07/14/2022, 3:34 PM
Trying to troubleshoot a completely different problem: https://kotlinlang.slack.com/archives/C19FD9681/p1657729271667769
It's super hard to test, especially since the publish plugin is closed source but looks like it could work
Longer term, it'd certainly be worth upgrading to
com.gradle.plugin-publish:1.0.0
Or maybe stop releasing to the Gradle Portal altogether? I forgot all the details but I think it proxies MavenCentral anyways
So you'd only loose the "UI" and discoverability of https://plugins.gradle.org/ but you'd gain consistent and open source publishing
3 Views