Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

This branch is 9 commits ahead, 2640 commits behind sbt:0.13

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
cache
compile
interface
ivy
launch
licenses
main
project
run
sbt
sbt_pending
scripted
src/main/conscript
tasks
testing
util
.gitignore
LICENSE
NOTICE
README.md
api.specification
launch.specification
scripted.specification

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
    
  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.

Something went wrong with that request. Please try again.