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,586 Commits 29 Branches 309 Tags 66 MiB
Scala 94.5%
Java 3.1%
Shell 1.1%
Batchfile 0.9%
Roff 0.2%
Other 0.1%
Go to file
Chris Birchall 483e7f68f2 Typo: Fixed the link to the "Setup" wiki page in the README 2011-10-21 10:01:50 +09:00
cache lazy InputCache for recursive caches 2011-06-20 15:25:23 -04:00
compile preserve API information needed for detecting annotations on defs. fixes #232 2011-10-19 22:23:47 -04:00
interface preserve API information needed for detecting annotations on defs. fixes #232 2011-10-19 22:23:47 -04:00
ivy drop configurations when storing unavailable classifiers. fixes #46 2011-10-16 17:27:36 -04:00
launch fixes #226. allow launched applications to signal the launcher's job is complete by returning Continue 2011-10-14 19:53:01 -04:00
licenses move remaining pieces of sbt subproject to sbt_pending and fix notices 2010-09-21 21:55:50 -04:00
main give builders access to resolved build before deciding if they are applicable 2011-10-18 22:49:09 -04:00
project store hashes of API instead of full API. fixes #21 2011-10-05 18:09:27 -04:00
run task execution interruptible using ctrl+c. fixes #228,#229 2011-10-18 22:43:25 -04:00
sbt merge Scoped{Setting,Task,Input} and {Setting,Task,Input}Key 2011-10-16 17:27:36 -04:00
sbt_pending drop more migrated pending items 2011-04-20 18:31:37 -04:00
scripted put scripted-plugin in the sbt package 2011-10-16 17:27:36 -04:00
src/main/conscript merge changes for 0.11.0 2011-09-24 20:42:29 -04:00
tasks Task state. 2011-09-21 22:54:46 -04:00
testing support use of native libraries in 'run' and 'test' 2011-08-05 21:56:32 -04:00
util task execution interruptible using ctrl+c. fixes #228,#229 2011-10-18 22:43:25 -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 Typo: Fixed the link to the "Setup" wiki page in the README 2011-10-21 10:01:50 +09:00
api.specification Spelling fixes. 2011-09-14 12:18:48 +07: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. See Setup for getting started with the latest binary release or see below to build from source.

sbt 0.7.7 and earlier versions are hosted on Google Code.

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.

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.11, which contains the latest code for the 0.11.x series. To build a specific release or commit, switch to the associated tag. The tag for the latest stable release is v0.11.0:

     $ git checkout v0.11.0

    Note that sbt is always built with the previous stable release. For example, the 0.11 branch is built with 0.11.0, the v0.11.0 tag is built with 0.10.1, and the v0.10.1 tag is built with 0.10.0.

  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.11.0 tag, the full location is:

     <xsbt>/target/sbt-launch-0.11.0.jar

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

     <xsbt>/target/sbt-launch-0.11.1-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 project/boot/ directory in the project in which you want to use the locally built sbt. 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.11.1-SNAPSHOT.