-
Notifications
You must be signed in to change notification settings - Fork 131
Update to sbt-scala-module 1.0.12 #120
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
Conversation
62d3150
to
573b876
Compare
Add osgi settings only to the `JVM` project. In the JS project they caused the resulting jar to be empty. Fixes scala#119 Adds MiMa checking to the JS jar. Minor cleanups in the build definition.
@gourlaysama this is ready for review now. Once it's merged we should release 1.0.7. I tested the fix for #119 locally
|
settings( | ||
name := "scala-parser-combinators-root", | ||
repoName := "scala-parser-combinators", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uh, that was probably a mistake from my part, i think it should stay name
. the plugin then sets repoName := name.value
, which could be overridden if necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't cause harm because the name
is picked up from the project name, so you get
> name
[info] scala-parser-combinatorsJS/*:name
[info] scala-parser-combinators
[info] scala-parser-combinatorsJVM/*:name
[info] scala-parser-combinators
But we should fix it anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not be 1.0.7 released? |
Add osgi settings only to the
JVM
project. In the JS project theycaused the resulting jar to be empty.
Fixes #119
Adds MiMa checking to the JS jar.
Minor cleanups in the build definition.