sbt/README.md

71 lines
3.4 KiB
Markdown
Raw Normal View History

2011-06-03 00:35:25 +02:00
[Google Code]: http://code.google.com/p/simple-build-tool
[Northeast Scala Symposium]: http://www.nescala.org/2011/
2011-09-25 01:13:04 +02:00
[Scala Days 2011]: http://days2011.scala-lang.org/node/138/285
[documentation]: http://www.scala-sbt.org/release/docs/
[Setup]: http://www.scala-sbt.org/release/docs/Getting-Started/Setup
[video of a demo]: http://vimeo.com/20263617
[FAQ]: http://www.scala-sbt.org/release/docs/faq
2011-03-24 01:31:47 +01:00
2012-05-11 00:47:34 +02:00
# sbt 0.13
2012-05-11 00:47:34 +02:00
This is the 0.13.x series of sbt.
2012-02-06 21:27:30 +01:00
* [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
2011-02-17 22:27:43 +01:00
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.
2011-02-17 22:27:43 +01:00
2011-09-01 02:58:09 +02:00
$ git clone git://github.com/harrah/xsbt.git
$ cd xsbt
2011-02-17 22:27:43 +01:00
3. 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:
2011-02-17 22:27:43 +01:00
$ git checkout v0.12.1
2011-02-17 22:27:43 +01:00
Note 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.
4. To build the launcher, publish all components locally, and build API and SXR documentation:
2011-02-17 22:27:43 +01:00
2011-09-01 02:58:09 +02:00
$ sbt build-all
2011-06-10 14:08:32 +02:00
2011-09-01 02:58:09 +02:00
Alternatively, the individual commands run by `build-all` may be executed directly:
2011-06-10 14:08:32 +02:00
2011-09-01 02:58:09 +02:00
$ sbt publish-local proguard sxr doc
2011-02-17 22:27:43 +01:00
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.1 tag, the full location is:
2011-02-17 22:27:43 +01:00
<xsbt>/target/sbt-launch-0.12.1.jar
2011-03-06 22:02:41 +01:00
2012-04-14 00:33:00 +02:00
If using the 0.13 development branch, the launcher is at:
2011-03-06 22:02:41 +01:00
2012-04-14 00:33:00 +02:00
<xsbt>/target/sbt-launch-0.13.0-SNAPSHOT.jar
## Modifying sbt
2012-06-03 21:37:00 +02:00
1. 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.
2012-04-14 00:33:00 +02:00
2. 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`.
2012-04-14 00:33:00 +02:00
3. To use your modified version of sbt in a project locally, run `publish-local`. If you have modified the launcher, also run `proguard`.
2012-04-14 00:33:00 +02:00
4. 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.
5. If a project has `project/build.properties` defined, either delete the file or change `sbt.version` to `0.13.0-SNAPSHOT`.
2012-09-15 00:08:35 +02:00
## Building Documentation
Documentation is built using sphinx and requires some external programs and libraries to be manually installed first:
2012-09-15 00:08:35 +02:00
```text
$ 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`.