Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scala packages don't follow naming convention #237

Open
mosaic-matt-bush opened this issue Aug 2, 2019 · 2 comments
Open

scala packages don't follow naming convention #237

mosaic-matt-bush opened this issue Aug 2, 2019 · 2 comments

Comments

@mosaic-matt-bush
Copy link

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?

@spullara
Copy link
Owner

spullara commented Aug 2, 2019

The community has been supporting the Scala stuff. Can you submit a PR?

@mosaic-matt-bush
Copy link
Author

I opened #248 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants