Adriaan Moors
cb0e723923
goal: a representation of a type reference to a refinement class that's stable across compilation runs (and thus insensitive to typing from source or unpickling from bytecode) problem: the current representation, which corresponds to the owner chain of the refinement: 1. is affected by pickling, so typing from source or using unpickled symbols give different results (because the unpickler "localizes" owners -- this could be fixed in the compiler in the long term) 2. can't distinguish multiple refinements in the same owner (this is a limitation of SBT's internal representation and cannot be fixed in the compiler) solution: expand the reference to the corresponding refinement type: doing that recursively may not terminate, but we can deal with that by approximating recursive references (all we care about is being sound for recompilation: recompile iff a dependency changes, and this will happen as long as we have one unrolling of the reference to the refinement)
sbt 0.13
This is the 0.13.x series of sbt.
- 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
-
Install the current stable binary release of sbt (see Setup), which will be used to build sbt from source.
-
Get the source code.
$ git clone git://github.com/harrah/xsbt.git $ cd xsbt -
The initial branch is the development branch 0.13, which contains the latest code for the next major sbt release. To build a specific release or commit, switch to the associated tag. The tag for the latest stable release is v0.12.1:
$ git checkout v0.12.1Note that sbt is always built with the previous stable release. For example, the 0.13 branch is built with 0.12.1, the v0.11.2 tag is built with 0.11.1, and the v0.11.0 tag is built with 0.10.1.
-
To build the launcher, publish all components locally, and build API and SXR documentation:
$ sbt build-allAlternatively, the individual commands run by
build-allmay be executed directly:$ sbt publish-local proguard sxr doc -
To use this locally built version of sbt, copy your stable
~/bin/sbtscript to~/bin/xsbtand change it to use the launcher jar in<xsbt>/target/. For the v0.12.1 tag, the full location is:<xsbt>/target/sbt-launch-0.12.1.jarIf using the 0.13 development branch, the launcher is at:
<xsbt>/target/sbt-launch-0.13.0-SNAPSHOT.jar
Modifying sbt
-
New development takes place on the 0.13 branch. Fixes and improvements that are binary compatible with 0.12 can be backported to the 0.12 branch at the time of the next release.
-
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, runcompile. -
To use your modified version of sbt in a project locally, run
publish-local. If you have modified the launcher, also runproguard. -
After each
publish-local, clean the~/.sbt/boot/directory. Alternatively, if sbt is running and the launcher hasn't changed, runreboot fullto have sbt do this for you. -
If a project has
project/build.propertiesdefined, either delete the file or changesbt.versionto0.13.0-SNAPSHOT.
Building Documentation
Documentation is built using sphinx and requires some external programs and libraries to be manually installed first:
$ pip install pygments
$ pip install sphinx
$ pip install sphinxcontrib-issuetracker
To build the full site, run the make-site task, which will generate the manual, API, SXR, and other site pages in target/site/.
To only work on the site and not API or SXR, run sphinx:mappings.