From e83013bc805f9ee3f9c9edfa838a41ba51fe8348 Mon Sep 17 00:00:00 2001 From: Jakob Odersky Date: Sun, 5 Jun 2016 19:26:53 -0700 Subject: update readme --- README.md | 4 ++-- 1 file 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 -- cgit v1.2.3