Scaladex

Travis Gitter

How it works

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

You can also watch The Last 10 Percent by Stefan Zeiger.

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.
    • 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 https://github.com/sbt/sbt/issues/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

Count Badge

Latest version

Count Badge

Latest version

For more information read the shields.io API