diff options
| author | Jakob Odersky <jakob@odersky.com> | 2017-08-11 14:34:31 -0700 |
|---|---|---|
| committer | Jakob Odersky <jakob@odersky.com> | 2017-08-26 16:08:18 -0700 |
| commit | 3d2c3d07cab51ab0cb9cec5edfe14e3c37c8e68e (patch) | |
| tree | 46bcacf2256464c3ba0b74c555fd7e91d5b87faa /README.md | |
| parent | 1eb62d92fd638b129564dd910d68f4e291719220 (diff) | |
| download | sbt-jni-3d2c3d07cab51ab0cb9cec5edfe14e3c37c8e68e.tar.gz sbt-jni-3d2c3d07cab51ab0cb9cec5edfe14e3c37c8e68e.tar.bz2 sbt-jni-3d2c3d07cab51ab0cb9cec5edfe14e3c37c8e68e.zip | |
Support sbt 1.0.0
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -186,10 +186,10 @@ Real-world use-cases of sbt-jni include: The goal of sbt-jni is to be the least intrusive possible. No transitive dependencies are added to projects using any plugin (some dependencies are added to the `provided` configuration, however these do not affect any downstream projects). ## Building -Both the macro library (`sbt-jni-macros`) and the sbt plugins (`sbt-jni`) are published. This project uses sbt-doge to allow cross-building on a per-project basis: +Both the macro library (`sbt-jni-macros`) and the sbt plugins (`sbt-jni`) are published. Cross-building happens on a per-project basis: - sbt-jni-macros is built against Scala 2.10, 2.11 and 2.12 -- sbt-jni is built against Scala 2.10 (the Scala version that sbt 0.13 uses) +- sbt-jni is built against Scala 2.12 (the Scala version that sbt 1.x uses) The differing Scala versions make it necessary to always cross-compile and cross-publish this project, i.e. append a "+" before every task. |