luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
sbt, the interactive build tool
1,866 Commits 29 Branches 309 Tags 68 MiB
Scala 94.5%
Java 3.1%
Shell 1.1%
Batchfile 0.9%
Roff 0.2%
Other 0.1%
Go to file
Eugene Vigdorchik e3a7a331d5 Changes after review, step 1. 2012-04-02 10:46:13 +04:00
cache lazy InputCache for recursive caches 2011-06-20 15:25:23 -04:00
compile delete empty parent directories of deleted class files. fixes #387 2012-03-05 13:40:17 -05:00
interface Macro def aware recompilation. 2012-03-04 17:35:51 +01:00
ivy Update Resolver configuration 2012-03-12 05:25:12 +05:30
launch support setting sbt.version from system property, which overrides setting in a properties file 2012-02-07 21:52:37 -05:00
licenses move remaining pieces of sbt subproject to sbt_pending and fix notices 2010-09-21 21:55:50 -04:00
main Changes after review, step 1. 2012-04-02 10:46:13 +04:00
project \'fork in test\' initial implementation. 2012-04-01 11:44:05 +04:00
run Prevent 'radio silence' for ForkRun.run(). 2011-11-10 15:47:25 +05:30
sbt test-quick test. 2012-03-10 19:52:57 +04:00
sbt_pending drop more migrated pending items 2011-04-20 18:31:37 -04:00
scripted No need for scalaVersion suffix in scripted dependency 2012-03-11 18:47:51 +05:30
src/main/conscript org.scala-tools.sbt -> org.scala-sbt and dropping scala-tools.org from defaults 2012-01-22 22:06:52 -05:00
tasks cleanup, fix compilation 2012-02-19 22:41:26 -05:00
testing \'fork in test\' initial implementation. 2012-04-01 11:44:05 +04:00
util \'fork in test\' initial implementation. 2012-04-01 11:44:05 +04:00
.gitignore merge changes for 0.11.0 2011-09-24 20:42:29 -04:00
LICENSE * move Environment classes to util/env module 2010-07-14 19:24:50 -04:00
NOTICE * move Environment classes to util/env module 2010-07-14 19:24:50 -04:00
README.md update README for 0.12.0-M1 2012-02-20 20:44:35 -05:00
api.specification Macro def aware recompilation. 2012-03-04 17:35:51 +01:00
launch.specification Spelling fixes. 2011-09-14 12:18:48 +07:00
scripted.specification New scripted test framework 2009-11-09 09:34:52 -05:00

README.md

sbt 0.11

This is the 0.11.x series of sbt (soon to be 0.12.x).

  • Setup: Describes getting started with the latest binary release. See below to build from source.
  • FAQ: Explains how to get help, how to report an issue, and how to contribute.
  • There is a video of a demo given at Scala Days 2011 based on sbt 0.10.0 that gives an introduction to the configuration system in sbt 0.10.0 and later. See the documentation for current information.
  • Google Code: hosts sbt 0.7.7 and earlier versions

Build from source

  1. Install the current stable binary release of sbt (see Setup), which will be used to build sbt from source.

  2. Get the source code.

     $ git clone git://github.com/harrah/xsbt.git
 $ cd xsbt

  3. The initial branch is the development branch 0.12, which contains the latest code for the 0.12.x series. To build a specific release or commit, switch to the associated tag. The tag for the latest stable release is v0.12.0-M1:

     $ git checkout v0.12.0-M1

    Note that sbt is always built with the previous stable release. For example, the 0.12 branch is built with 0.12.0-M1, the v0.11.2 tag is built with 0.11.1, and the v0.11.0 tag is built with 0.10.1.

  4. To build the launcher, publish all components locally, and build API and SXR documentation:

     $ sbt build-all

    Alternatively, the individual commands run by build-all may be executed directly:

     $ sbt publish-local proguard sxr doc

  5. To use this locally built version of sbt, copy your stable ~/bin/sbt script to ~/bin/xsbt and change it to use the launcher jar in <xsbt>/target/. For the v0.12.0-M1 tag, the full location is:

     <xsbt>/target/sbt-launch-0.12.0-M1.jar

    If using the 0.12 development branch, the launcher is at:

     <xsbt>/target/sbt-launch-0.12.0-SNAPSHOT.jar

Modifying sbt

When developing sbt itself, there is no need to run build-all, since this generates documentation as well. For the fastest turnaround time for checking compilation only, run compile.

To use your modified version of sbt in a project locally, run publish-local. If you have modified the launcher, also run proguard.

After each publish-local, clean the ~/.sbt/boot/ directory. Alternatively, if sbt is running and the launcher hasn't changed, run reboot full to have sbt do this for you.

If a project has project/build.properties defined, either delete the file or change sbt.version to 0.12.0-SNAPSHOT.