aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakob Odersky <jakob@odersky.com>2016-06-05 19:26:53 -0700
committerJakob Odersky <jakob@odersky.com>2016-06-05 19:26:53 -0700
commite83013bc805f9ee3f9c9edfa838a41ba51fe8348 (patch)
treec2ab778f7fbea715d08f6e119f2f33cc8674aad3
parent0e579c9519d7adc9d1872915d820632334ddc134 (diff)
downloadsbt-jni-e83013bc805f9ee3f9c9edfa838a41ba51fe8348.tar.gz
sbt-jni-e83013bc805f9ee3f9c9edfa838a41ba51fe8348.tar.bz2
sbt-jni-e83013bc805f9ee3f9c9edfa838a41ba51fe8348.zip
update readme
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 56e350f..fea0c0e 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ The second point, portability, is inherent to JNI and thus unavoidable. However
All plugins are made available with the following sbt configuration
```scala
-addSbtPlugin("ch.jodersky" % "sbt-jni" % "1.0.0")
+addSbtPlugin("ch.jodersky" % "sbt-jni" % "1.0.1")
```
in `project/plugins.sbt`.
@@ -174,7 +174,7 @@ The [plugins' unit tests](plugin/src/sbt-test/sbt-jni) offer some simple example
Real-world use-cases of sbt-jni include:
-- [serial communication library for scala](https://github.com/jodersky/flow/tree/akka-serial)
+- [serial communication library for scala](https://github.com/jodersky/flow)
## Requirements and Dependencies