scala packages don't follow naming convention

The standard naming convention for scala libraries is to append the scala version to the artifact ID, after an underscore. The scala-extensions artifact uses a dash to before the version number.

This is a problem for projects that cross-compile against multiple scala versions, since we can't use SBT's built-in means of handling this, the %% operator, which automatically detects the scala version being used:

// sbt syntax for java libraries, fetches an artifact named compiler
"com.github.spullara.mustache.java" % "compiler" % "0.9.6",
// sbt syntax for scala libraries; tries and fails to fetch an artifact named scala-extensions_2.11, scala-extensions_2.12, etc, depending on the scala version
"com.github.spullara.mustache.java" %% "scala-extensions" % "0.9.6"

Can you update your scala artifact names to use an underscore instead of a dash? Maybe you could address #156 at the same time?

Start by locating the build and publishing configuration for the scala-extensions artifact and compare its generated names with the Scala cross-compilation convention described here. Review issue #156 for related scope, then verify that published artifacts use underscore-separated Scala versions and can be resolved through SBT's %% operator.