sbt, the interactive build tool
Go to file
Mark Harrah 2a84a80d5b clean up scalaOrg changes 2012-04-12 17:31:28 -04:00
cache lazy InputCache for recursive caches 2011-06-20 15:25:23 -04:00
compile Improved implementation for `parents` accumulation for java classes 2012-03-27 01:40:10 +05:30
interface print-warnings task for Scala 2.10+ to avoid needing to rerun 'compile' to see deprecation/unchecked warnings 2012-03-17 19:31:55 -04:00
ivy configuration via ivysettings.xml: use URI instead of URL and make 'inter-project' resolver available for multi-project builds. ref #416 2012-04-11 22:40:45 -04:00
launch clean up scalaOrg changes 2012-04-12 17:31:28 -04:00
licenses move remaining pieces of sbt subproject to sbt_pending and fix notices 2010-09-21 21:55:50 -04:00
main Merge 'vjovanov/0.12' into 0.12 2012-04-12 17:21:08 -04:00
project merge test forking from vigdorchik/xsbt/wip_fork_test 2012-04-06 20:48:31 -04:00
run Prevent 'radio silence' for ForkRun.run(). 2011-11-10 15:47:25 +05:30
sbt configuration via ivysettings.xml: use URI instead of URL and make 'inter-project' resolver available for multi-project builds. ref #416 2012-04-11 22:40:45 -04:00
sbt_pending drop more migrated pending items 2011-04-20 18:31:37 -04:00
scripted Fixed scripted-plugin's reflection call 2012-03-17 19:31:55 -04:00
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 Revert "work around for 2.10. pattern matching on KNil now requires KNil()" 2012-03-17 22:58:13 -04:00
testing move ForkMain.Tags out to top-level ForkTags to make sxr happy 2012-04-06 23:29:48 -04:00
util clean up scalaOrg changes 2012-04-12 17:31:28 -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 0.12.0-M2 2012-03-14 20:39:02 -04: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-M2:

     $ git checkout v0.12.0-M2
    

    Note that sbt is always built with the previous stable release. For example, the 0.12 branch is built with 0.12.0-M2, 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-M2 tag, the full location is:

     <xsbt>/target/sbt-launch-0.12.0-M2.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.