Dokka: Please publish the plugin to maven central

[mhshams]

It would be nice to have the plugin in maven central repository

[io7m]

I can assist with this, if necessary.

[vietj]

yes, please no kidding

[jangalinski]

This really would be a great enhancement. Background: in an enterprise project, we have limited access to "the web" (via proxy) and thus cannot not arbitrary use the repositories-config in a pom, it will not be reachable. And we cannot just add a "less popular" repo like jcenter/bintray/... to company-central nexus since we do not have permissions. Currently, we just cannot use the plugin. Its not that hard and I also could assist or even run this on our jenkins if required.

[benjamin-bader]

Please do publish dokka to Maven Central.

My company does not support JFrog for ethical reasons, and unfortunately that means we cannot make use of this plugin until it's at least hosted somewhere in addition to jcenter.

Thanks!

EDIT:

I missed that this is published to Gradle Plugin Portal; that helps me. I'd still encourage you to use Maven Central by default. As jcenter mirrors everything in Central, it would only increase number of projects that can use dokka.

Also, "my company" does _not_ refer to Microsoft here!

[hannesa2]

JFrog for ethical reasons

I'm interested in what your company reason to give them the attribute not-supportable

[benjamin-bader]

I can sum it up by saying, "We choose not to do business with jerks". I don't expect others to follow suit, but that's the position.

[sdeleuze]

Could we please move forward on this issue and publish Dokka 1.4.10+ artifacts to Maven Central? That would simplify the setup in Spring Framework where we are about to use it, but also in other Spring projects.

Since you chose to use Kotlin versioning (despite the alpha status), current lack of deployment in Central produces IMO unnecessary noise. The fact that Dokka needs to be used both on plugins and dependency side make this even more needed. Also I don't think artifact names are likely to change so that's another reason for such move.

Notice that probably means that transitive dependencies like kotlinx.html should be published on Central as well.

[hannesa2]

Is this an option ? https://jitpack.io/#Kotlin/dokka/1.4.0

[sdeleuze]

@hannesa2 I don't think Jitpack will help here, Dokka packages are already available from Bintray.

More details about my use case which is IMO not unusual in real projects:

• I can't use JCenter because it overlaps with Maven Central which is a no go for us
• I tried to specify individual repositories with https://dl.bintray.com/kotlin/dokka and https://dl.bintray.com/kotlin/kotlinx.html
• Could not find org.jetbrains.kotlinx:kotlinx-html-jvm:0.7.2 because https://dl.bintray.com/kotlin/kotlinx.html only contains 0.7.1 versions and previous not 0.7.2
  
  
  
  • Ok so I update the repo to the new one https://kotlin.bintray.com/kotlinx
  
  
  • New error Could not find org.jetbrains:markdown:0.1.45
  
  
  • Let's add https://dl.bintray.com/jetbrains/markdown/
  
  
  • It works
  
  

I had to add 3 additional repositories to 2 different places in my Gradle config -> I can't reasonably commit that in Spring Framework. Add to this the fact that it is pretty hard to understand why repositories for a Gradle plugin should be specified in repositories { } in addition to pluginManagement { repositories { } }.

So please, fix this (you can shade those transitive dependencies if you don't want to publish them to Central) and deploy upcoming release of Dokka 1.4 to Central. Dokka 1.4.x are considered as alpha but I think Dokka 0.x had also the same level of maturity and we need to document our projects, so IMO this is a better strategy to help us leveraging Dokka 1.4.x with the knowledge that breaking changes (with upgrade paths) will happen. Would shading avoid the need for repositories { } declarations?

[ZacSweers]

Ethical issues aside, jcenter has exhibited reliability issues over the years due to artifact integrity concerns and a general lax security around package uploads (https://blog.autsoft.hu/a-confusing-dependency/). It's not just a matter of preference, but rather that every consumer of Dokka has to add this extra gradle ceremony just to _safely_ add jcenter.

repositories {
  //... other repos
  exclusiveContent {
    forRepository {
      maven {
        name = "JCenter"
        setUrl("https://jcenter.bintray.com/")
      }
    }
    filter {
      // Required for Dokka
      includeModule("org.jetbrains.kotlinx", "kotlinx-html-jvm")
      includeGroup("org.jetbrains.dokka")
      includeModule("org.jetbrains", "markdown")
    }
  }
}

[ibauersachs]

1.4.10.2 appeared on Maven Central today, but at least org.jetbrains:markdown as a required dependency is also not available.

[ZacSweers]

1.4.20 however did not make it to maven central