Scaladex

How it works

We pull poms from Bintray and we receive poms from Maven Central (Sonatype) or to Scaladex directly. Your library has to be published to one of those repositories.

• How to publish on Maven Central
• How to publish on Bintray
• How to publish on Scaladex

Process:

• Releases Sources
  • Push from Maven Central (Sonatype):
    • We receive pushes from Maven Central that follow the scala artifactId convention. A common practice is to include the scala compiler version in the artifactId. The .pom files will contain _2.10, _2.11, _2.12 or any further Scala Version.
  • Push from Scala Developers:
    • You can use the sbt-scaladex to push releases
    • You can also use the publish REST api
  • Pull Bintray (once per day):
    • File Search: releases that follow the scala artifactId convention presented above.
    • Non Standards: If you dont follow this convention add your releases to non-standard.json
    • Sbt Plugins: We index sbt plugins published to sbt/sbt-plugin-releases add your plugin to claims.json
• We download pom and parent poms
• We read them, 10% are invalid (most common issue: duplicated tags see sbt/sbt#2566)
• We inspect the pom file for scm tag (source control management). If you forgot to add a scm tag claim your library or you publish a sbt plugin add claim your project to claims.json
• We download content and metadata from GitHub (Readme, Avatar, Descriptions, etc)

How to contribute

Join the gitter.im channel and read the developer guide

Badges API

For more information read the shields.io API