From 9faf45edabe4ec0b71aa27d759bec952bd769dce Mon Sep 17 00:00:00 2001 From: Jakob Odersky Date: Tue, 3 Jan 2017 00:06:41 +0100 Subject: Clarify meaning of latest version --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 411cb89..d7f39f5 100644 --- a/README.md +++ b/README.md @@ -25,12 +25,12 @@ The second point, portability, is inherent to JNI and thus unavoidable. However | JniNative | Adds sbt wrapper tasks around native build tools to ease building and integrating native libraries. | | JniPackage | Packages native libraries into multi-platform fat jars. No more manual library installation! | -All plugins are made available with the following sbt configuration +All plugins are made available by adding the following to `project/plugins.sbt`: ```scala addSbtPlugin("ch.jodersky" % "sbt-jni" % "") ``` -in `project/plugins.sbt`. +where `` refers to the version indicated by the download badge above, or, equivalently, to the [latest version available on bintray](https://bintray.com/jodersky/sbt-plugins/sbt-jni/_latestVersion). Note that most plugins are enabled in projects by default. Disabling their functionality can be achieved by adding `disablePlugins()` to the corresponding project definition (for example, should you wish to disable packaging of native libraries). @@ -169,7 +169,7 @@ This plugin packages native libraries produced by JniNative in a way that they c The [plugins' unit tests](plugin/src/sbt-test/sbt-jni) offer some simple examples. They can be run individually through these steps: 1. Publish the macros library locally `sbt publishLocal`. -2. Change to the test's directory and run `sbt -Dplugin.version=-SNAPSHOT`. +2. Change to the test's directory and run `sbt -Dplugin.version=`. 3. Follow the instructions in the `test` file (only enter the lines that start with ">" into sbt). Real-world use-cases of sbt-jni include: -- cgit v1.2.3