From f946be87b81cc9cb040ab5e3f8a5195a915ad1e4 Mon Sep 17 00:00:00 2001 From: Christopher Vogt Date: Wed, 27 Apr 2016 09:55:00 -0400 Subject: minor improvements to docs, imports, visibilities --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 84259da..2485518 100644 --- a/README.md +++ b/README.md @@ -71,16 +71,16 @@ You can see how your build is configured via overrides. call `cbt` to see a full list of available commands for this build. -Look into the class `DefaultBuild` in CBT's source code to see their +Look into the class PackageBuild (and it's super class BasicBuild) in CBT's source code to see their details. The source code is really simple. Don't shy away from looking, even as a beginner. No crazy stuff, I promise ;). You -can find the relevant code in CBT's `stage2/DefaultBuild.scala` +can find the relevant code in CBT's stage2/BasicBuild.scala I order to keep executing the same command triggered by file changes use `cbt loop `. You can find example builds in CBT's own `test/` folder. Not all of them have a build file, in which case CBT uses the default -`cbt.DefaultBuild`. +cbt.BasicBuild. A folder `build/` can have its own folder `build/` inside in order to add source or maven dependencies to your build. Eventually -- cgit v1.2.3