buildr 1.3.4 → 1.3.5

data/doc/preface.textile

@@ -2,27 +2,53 @@
 layout: preface
 ---
 
-div(title). !{width:20em}images/buildr-hires.png!
+p(title). !images/zbuildr.png!
 
-#(toc) "Getting Started":getting_started.html
-# "Projects":projects.html
-# "Building":building.html
-# "Artifacts":artifacts.html
-# "Packaging":packaging.html
-# "Testing":testing.html
-# "Settings & Profiles":settings_profiles.html
-# "Languages":languages.html
-# "More Stuff":more_stuff.html
-# "Extending Buildr":extending.html
-# "Contributing":contributing.html
+<ol class='toc'>
+  <li>"Quick Start":quick_start.html</li>
+  <li>"Installing and Running":installing.html</li>
+  <li>"Projects":projects.html</li>
+  <li>"Building":building.html</li>
+  <li>"Artifacts":artifacts.html</li>
+  <li>"Packaging":packaging.html</li>
+  <li>"Testing":testing.html</li>
+  <li>"Settings & Profiles":settings_profiles.html</li>
+  <li>"Languages":languages.html</li>
+  <li>"More Stuff":more_stuff.html</li>
+  <li>"Extending Buildr":extending.html</li>
+  <li>"Contributing":contributing.html</li>
+</ol>
 
 
-p(preface). Copyright 2007-2009 Apache Buildr
+p(preface).  !images/asf-logo.png!
+
+Copyright 2007-2009 Apache Buildr
 
 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
 
-"http://www.apache.org/licenses/LICENSE-2.0":http://www.apache.org/licenses/LICENSE-2.0
+  http://www.apache.org/licenses/LICENSE-2.0
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-p(preface). <blank>
+
+
+<div class='preface quotes'>
+"Daniel Spiewak":http://www.codecommit.com/blog:
+
+bq. If you think about it, the question isn’t “Why use Buildr?”, it’s really “Why use anything else?” The advantages afforded by Buildr are so substantial, I really can’t see myself going with any other tool, at least not when I have a choice.
+
+"Tristan Juricek":http://tristanhunt.com/:
+
+bq. That’s still the strongest sell: it builds everything I need, and as I’ve needed more, I just got things working without a lot of fuss.
+
+"Matthieu Riou":http://offthelip.org/:
+
+bq. We used to rely on Ant, with a fairly extensive set of scripts. It worked but was expensive to maintain. The biggest mistake afterward was to migrate to Maven2. I could write pages of rants explaining all the problems we ran into and we still ended up with thousands of lines of XML.
+
+"Martin Grotzke":http://www.javakaffee.de/blog/:
+
+bq. The positive side effect for me as a java user is that I learn a little ruby, and that’s easy but lots of fun… :-)
+</div>
+
+
+p(preface).  

data/doc/projects.textile

@@ -12,7 +12,6 @@ Feed it a project definition, and Buildr will set up all these tasks for you. Th
 
 The remainder of this guide deals with what it takes to build a project.  But first, let's pick up a sample project to work with.  We'll call it _killer-app_:
 
-<notextile>
 {% highlight ruby %}
 require 'buildr'
  
@@ -58,7 +57,6 @@ define 'killer-app' do
 
 end
 {% endhighlight %}
-</notextile>
 
 A project definition requires four pieces of information: the project name, group identifier, version number and base directory.  The project name ... do we need to explain why its necessary?  The group identifier and version number are used for packaging and deployment, we'll talk more about that in the "Packaging":packaging.html section.  The base directory lets you find files inside the project.
 
@@ -102,7 +100,6 @@ The @projects@ method takes a list of names and returns a list of projects.  If
 
 Let's illustrate this with a few examples:
 
-<notextile>
 {% highlight ruby %}
 puts projects.inspect
 => [project("killer-app"), project("killer-app:teh-api") ... ]
@@ -119,7 +116,6 @@ puts project('killer-app:teh-api').inspect
 puts project('killer-app').project('teh-api').inspect
 => project("killer-app:teh-api")
 {% endhighlight %}
-</notextile>
 
 To see a list of all projects defined in your Buildfile run @buildr help:projects@.
 
@@ -128,7 +124,6 @@ h2(#tasks). Running Project Tasks
 
 Most times, you run tasks like @build@ or @package@ that operate on the current project and recursively on its sub-projects.  The "current project" is the one that uses the current working directory.  So if you're in the @la-web/src@ directory looking at source files, _la-web_ is the current project.  For example: 
 
-<notextile>
 {% highlight sh %}
 # build killer-app and all its sub-projects
 $ buildr build
@@ -141,11 +136,9 @@ $ buildr test
 $ cd ../la-web
 $ buildr package
 {% endhighlight %}
-</notextile>
 
 You can use the project's full name to invoke one of its tasks directly, and it doesn't matter which directory you're in.  For example:
 
-<notextile>
 {% highlight sh %}
 # build killer-app and all its sub-projects
 $ buildr killer-app:build
@@ -156,11 +149,9 @@ $ buildr killer-app:teh-impl:test
 # package only la-web
 $ buildr killer-app:la-web:package
 {% endhighlight %}
-</notextile>
 
 Buildr provides the following tasks that you can run on the current project, or on a specific project by prefixing them with the project's full name:
 
-<notextile>
 {% highlight text %}
 clean     # Clean files generated during a build
 compile   # Compile all projects
@@ -172,7 +163,6 @@ package   # Create packages
 test      # Run all test cases
 uninstall # Remove previously installed packages
 {% endhighlight %}
-</notextile>
 
 To see a list of all the tasks provided by Buildr run @buildr help:tasks@.
 
@@ -183,7 +173,6 @@ We mentioned the group identifier, version number and base directory.  These are
 
 There are two ways to set project properties.  You can pass them as a hash when you call @define@, or use accessors to set them on the project directly.  For example:
 
-<notextile>
 {% highlight ruby %}
 define 'silly', :version=>'1.0' do
   project.group = 'acme'
@@ -194,7 +183,6 @@ puts project('silly').version
 puts project('silly').group
 => acme
 {% endhighlight %}
-</notextile>
 
 Project properties are inherited.  You can specify them once in the parent project, and they'll have the same value in all its sub-projects.  In the example, we only specify the version number once, for use in all sub-projects.
 
@@ -209,7 +197,6 @@ The @path_to@ method takes an array of strings and concatenates them into a path
 
 For example:
 
-<notextile>
 {% highlight ruby %}
 # Relative to the current project
 path_to('src', 'main', 'java')
@@ -220,7 +207,6 @@ _('src/main/java')
 # Relative to the teh-impl project
 project('teh-impl')._('src/main/java')
 {% endhighlight %}
-</notextile>
 
 
 h2(#defining). Defining The Project
@@ -229,7 +215,6 @@ The project definition itself gives you a lot of pre-canned tasks to start with,
 
 Since the project definition executes each time you run Buildr, you don't want to perform any work directly inside the project definition block.  Rather, you want to use it to specify how different build task work when you invoke them. Here's an example to illustrate the point:
 
-<notextile>
 {% highlight ruby %}
 define 'silly' do
   puts 'Running buildr'
@@ -239,7 +224,6 @@ define 'silly' do
   end
 end
 {% endhighlight %}
-</notextile>
 
 Each time you run Buildr, it will execute the project definition and print out "Running buildr".  We also extend the @build@ task, and whenever we run it, it will print "Building silly".  Incidentally, @build@ is the default task, so if you run Buildr with no arguments, it will print both messages while executing the build.  If you run Buildr with a different task, say @clean@, it will only print the first message.
 
@@ -253,7 +237,6 @@ One project can reference another ahead of its definition.  If Buildr detects a
 
 In this example we define one project in terms of another, using the same dependencies, so we only need to specify them once:
 
-<notextile>
 {% highlight ruby %}
 define 'bar' do
   compile.with project('foo').compile.dependencies
@@ -263,7 +246,6 @@ define 'foo' do
   compile.with ..lots of stuff..
 end
 {% endhighlight %}
-</notextile>
 
 One last thing to remember.  Actually three, but they all go hand in hand.
 

data/doc/quick_start.textile

@@ -0,0 +1,210 @@
+---
+layout: default
+title: Quick Start
+---
+
+This quick start guide is meant to be a _very_ simple introduction to Buildr and its most basic concepts.  However, despite its basic level, we will still cover most of the concepts you will ever need to be productive with Buildr.  We will leave out some important things (like "sub-projects":projects.html), and we will over-simplify some other concepts (such as "artifacts":artifacts.html).  Nevertheless, most Buildr projects never need to go beyond the techniques contained within these pages.
+
+*No knowledge of Ruby is assumed.*  Buildr is designed to be a very intuitive, very easy-to-use tool.  You can create buildfiles which describe incredibly intricate projects, write custom tasks which do things far beyond Ant, and still never need to pick up more than a smattering of Ruby syntax.  With that said, if you do know Ruby, Buildr's DSL will seem very natural and welcoming.  We do assume that you have already "downloaded and installed":installing.html Buildr and are ready to put the tool to good use.
+
+
+h2(#first-project). Your First Project
+
+Much like Maven, Buildr is oriented around projects and tasks.  You define your project in a concise, declarative fashion and most common tasks (such as compilation and testing) will be made available to you "at no extra charge".  Most of the project definition is contained within the _buildfile_ -- or _Buildfile_, if you're really in love with the Make convention -- a single file sitting at the root of your project.  A project definition does not need to be any more complicated than the following:
+
+{% highlight ruby %}
+define 'killer-app'
+{% endhighlight %}
+
+h3. Compiling
+
+Of course, this isn't really giving Buildr much information.  What it can't learn from the buildfile, Buildr will figure out by inspecting your directory structure.  Java sources are expected to exist within the @src/main/java/@ directory.  If Buildr finds these sources, it will automatically configure the compilation to source that directory, depositing the results in the @target/classes/@ directory (all under the project directory of course).  We can run this compilation using the following command:
+
+{% highlight sh %}
+$ buildr compile
+{% endhighlight %}
+
+Information about the classpath and dependencies is described "later on":#dependencies.
+
+p(tip). By default, Buildr projects assume the Java language and the @src/main/java/@ source directory.  You can also have projects in the Scala or Groovy language (both languages support joint compilation with Java).  To use Scala, place your @.scala@ files in the @src/main/scala/@ directory and include the following invocation at the head of your buildfile: @require 'buildr/scala'@  Similarly, Groovy expects sources in the @src/main/groovy/@ directory and necessitates @require 'buildr/groovy'@ (see "languages":languages.html for more information).
+
+The @compile@ task will also detect _any_ files which exist under the @src/main/resources/@ directory.  These resources are copied verbatim to the @target/resources/@ directory as part of the compilation task.  Buildr also performs some basic change detection to minimize compilation.  If your source files haven't changed since the last compile, then they will not be recompiled.
+
+h3. Packaging
+
+At some point, we're going to want to wrap up our classes and produce a single JAR file for distribution.  Buildr can certainly help us with this, but we are going to need to provide it with a little bit more information.  Specifically, we need to say the type of package to produce (e.g. @:jar@, @:war@, etc) as well as the current version of our project.  This information is placed within the buildfile:
+
+{% highlight ruby %}
+define 'killer-app' do
+  project.version = '0.1.0'
+  package :jar
+end
+{% endhighlight %}
+
+The @project.version@ attribute can be any value you like.  Even non-numeric versions are perfectly acceptable (e.g. @'ikj-0.3.1-E'@).  This version -- coupled with the packaging information -- will be used to generate a JAR file: @killer-app-0.1.0.jar@.  As would be expected, this file is placed within the @target/@ directory when the following command is run:
+
+{% highlight sh %}
+$ buildr package
+{% endhighlight %}
+
+The @package@ task depends upon the @compile@ task, so if a rebuild is necessary prior to the creation of the JAR, Buildr will see to it.
+
+We can also chain tasks together in a single invocation.  For example, we may want to clean all of the old compilation results prior to recompiling and generating a packaged result:
+
+{% highlight sh %}
+$ buildr clean package
+{% endhighlight %}
+
+The @clean@ task simply removes the @target/@ directory, effectively wiping out any compilation results like class files or resources.
+
+h3. Directory Structure
+
+As you may have noticed, Buildr does have some default notions about what a project should look like and how it should be organized.  We think that these defaults are quite nice and make for a more navigable project.  However, we do understand that not all projects are exactly alike.  Buildr's "layouts":extending.html#layouts make it possible for any project to easily change these defaults.  For example, this would allow you to easily migrate a project that had been based on a different directory structure, such as the @src/@ and @bin/@ convention often used by Ant.
+
+
+h2(#dependencies). Dependencies
+
+So far, we have seen how Buildr can automatically infer what amounts to dozens of lines of @build.xml@ contents, all based on a buildfile and a directory structure.  However, the best is yet to come.  Buildr also provides Maven-style dependency management (but without the long loading times!).  In other words, you specify each dependent library using a string descriptor and Buildr figures out how to download and configure your classpath (the library descriptors are just a Ruby array, therefore they are separated by commas (@,@)).  You must specify at least one remote repository so that Buildr knows from where to download these libraries.  For example, we can configure our project to reference the "Apache Commons CLI":http://commons.apache.org/cli/ library and download libraries from the Ibiblio repository:
+
+{% highlight ruby %}
+repositories.remote << 'http://www.ibiblio.org/maven2'
+
+define 'killer-app' do
+  project.version = '0.1.0'
+  compile.with 'commons-cli:commons-cli:jar:1.2'
+  package :jar
+end
+{% endhighlight %}
+
+This sort of dependency declaration should look quite familiar if you are at all familiar with Maven.  The general format for an artifact descriptor is _groupId:artifactId:packageType:version_.  Any Maven artifacts included in this fashion will be retrieved from the "list of remote repositories":artifacts.html#repositories (in this case, Ibiblio) and installed in your local repository at @~/.m2/repository/@.
+
+p(tip). You can search the global repository of artifacts at sites like "MvnBrowser":http://www.mvnbrowser.com.  Simply enter the name of the library you are looking for, and the search should pull up the groupId, artifactId and a list of available versions.
+
+Unfortunately, not all libraries are quite as simple as Commons CLI.  Many libraries (such as Apache Wicket) have dependencies of their own.  While we may be able to _compile_ against Apache Wicket without these extra libraries on our classpath, we cannot actually _run_ our application without its transitive dependencies. To avoid tracking down each of these dependencies and adding them manually, we can simply use the @transitive@ directive (this is how Maven behaves by default):
+
+{% highlight ruby %}
+repositories.remote << 'http://www.ibiblio.org/maven2'
+
+define 'killer-app' do
+  project.version = '0.1.0'
+  compile.with transitive('org.apache.wicket:wicket:jar:1.4-rc6')
+  package :jar
+end
+{% endhighlight %}
+
+The @compile.with@ property accepts a full array of comma-separated artifacts, making it possible to specify any number of dependencies as necessary.  Of course, such a long list of verbose string descriptors could get very tiresome and messy.  For this reason, it is conventional to assign each dependency to a constant (e.g. @WICKET@) which is declared just above the project in the buildfile and passed to @compile.with@ in a clean, easy-to-read style:
+
+{% highlight ruby %}
+repositories.remote << 'http://www.ibiblio.org/maven2'
+
+WICKET = transitive('org.apache.wicket:wicket:jar:1.4-rc6')
+SLF4J = 'org.slf4j:slf4j-jdk14:jar:1.5.8'
+
+define 'killer-app' do
+  project.version = '0.1.0'
+  compile.with WICKET, SLF4J
+  package :jar
+end
+{% endhighlight %}
+
+Unfortunate as it may seem, not all libraries are available in Maven repositories.  While most of the major libraries (e.g. Hibernate, Spring, etc) are kept updated by intrepid volunteers, some of the more obscure frameworks are left out in the cold.  An example of one such framework is "DBPool":http://www.snaq.net/java/DBPool, a very fast connection pool designed to integrate with JDBC.  However, like most Java libraries, DBPool does provide a zip archive which contains the JAR file, as well as some documentation and perhaps a license or two.
+
+Almost magically, we can instruct Buildr to get the DBPool artifact from this URL.  Buildr will treat this download just like any other artifact, retrieving it when requried by the @compile@ task.  However, unlike a normal Maven artifact, Buildr will do some extra processing once the download is complete.  It will actually dig into the downloaded archive, detect and extract the JAR file, installing it into the local repository just like any other artifact:
+
+{% highlight ruby %}
+DBPOOL = 'net.snaq:dbpool:jar:4.8.3'
+download artifact(DBPOOL) => 'http://www.snaq.net/java/DBPool/DBPool_v4.8.3.zip'
+
+define 'killer-app' do
+  project.version '0.1.0'
+  compile.with DBPool
+  package :jar
+end
+{% endhighlight %}
+
+This is one area where Buildr's dependency management vastly excedes Maven's.  With Maven, you would have to install the DBPool dependency manually.  Buildr's auto-magical download and extraction keeps the dependency definitions centralized within the buildfile, available to your entire team and automatically resolved as needed by the compilation tasks.
+
+
+h2(#testing). Testing
+
+Buildr supports auto-magical integration with a number of mainstream testing frameworks.  For Java, this includes the ubiquitus JUnit4, as well as TestNG and a number of others.  Scala supports Specs and ScalaTest, while Groovy supports EasyB.  Configuration is as simple as placing your test sources in the appropriate directory.  In the case of JUnit or TestNG, this would be @src/test/java/@.  Once these tests are in place, we can run them using the @test@ task:
+
+{% highlight sh %}
+$ buildr test
+{% endhighlight %}
+
+When the @test@ task runs, it will ensure that your main sources are compiled, as well as the tests themselves.  In the case of JUnit4, test classes are auto-detected based on which base class they extend (@TestCase@).  These tests will be invoked using the special test classpath.  This classpath includes all of the dependencies passed to @compile.with@ along with the dependencies required for testing.  Thus, Buildr will actually go out and download JUnit 4.5 (if necessary) and place that JAR on the classpath in order to run your tests.  It is also possible to add artifacts specifically required for testing.  So, if your tests make use of the Commons Collections library, but your main sources do not, you can include that dependency only for the tests by using the @test.with@ property.  This functions identically to @compile.with@:
+
+{% highlight ruby %}
+define 'killer-app' do
+  project.version = '0.1.0'
+  compile.with 'commons-cli:commons-cli:jar:1.2'
+  test.with 'commons-collections:commons-collections:jar:3.2'
+  package :jar
+end
+{% endhighlight %}
+
+Of course, not everyone _likes_ JUnit4.  As mentioned previously, Buildr supports a number of test frameworks.  It is possible to use TestNG instead of JUnit4 by setting the @test.using@ property to @:testng@:
+
+{% highlight ruby %}
+define 'killer-app' do
+  project.version = '0.1.0'
+  compile.with 'commons-cli:commons-cli:jar:1.2'
+  test.with 'commons-collections:commons-collections:jar:3.2'
+  test.using :testng
+  package :jar
+end
+{% endhighlight %}
+
+Note that only one test framework per-project may be used.  This may seem like an obvious restriction given that both frameworks introduced so far have used the same directory, but other frameworks such as Specs and EasyB do not follow the same convention.  In cases of ambiguity (for example, when tests are present in both @src/test/java/@ _and_ @src/spec/scala/@), only one test framework will be chosen, but this choice is not well-defined.  When in doubt, explicitly specify the test framework with the @test.using@ property.  This overrides Buildr's auto-detection and ensures sane behavior.
+
+Other test frameworks are documented "here":testing.html and "here":languages.html.
+
+
+h2(#custom-tasks). Custom Tasks
+
+If there is one area in which Buildr excels, it is defining custom tasks.  This is something which is notoriously difficult in both Ant and Maven, often requiring separate Java plugins and mountains of code simply to perform basic tasks.  For example, let's imagine that we wanted to define a @run@ task which would compile and run our "killer-app" project.  This is a simple matter of invoking the @java@ command against our main class:
+
+{% highlight ruby %}
+define 'killer-app' do
+  project.version = '0.1.0'
+  package :jar
+  
+  task :run => :compile do
+    system 'java -cp target/classes org.apache.killer.Main'
+  end
+end
+{% endhighlight %}
+
+This code defines a new task, @run@, which depends upon the @compile@ task.  This task only performs a single operation: it invokes the @system@ method, passing the relevant command as a string.  Note that the @system@ method documentation may be found "here":http://www.ruby-doc.org/core/classes/Kernel.html#M005971.  Tasks use real Ruby (actually, the entire buildfile is real Ruby too), so if you are familiar with that language, then you should be right at home writing custom tasks in Buildr.  We can invoke this task in the following way:
+
+{% highlight sh %}
+$ buildr killer-app:run
+{% endhighlight %}
+
+This works, but it's clumsy.  The reason we had to give the "@killer-app:@" prefix is because we defined the @run@ task _within_ our project, rather than outside of the @define@ block.  However, if we define @run@ outside of the project, then we don't really have access to the @compile@ task (which is project-specific).  The solution here is a bit of magic known as @local_task@.  This is how tasks like @compile@ and @test@, which are technically project-specific (think: instance methods) can be invoked without the fully-qualified project name:
+
+{% highlight ruby %}
+local_task :run
+
+define 'killer-app' do
+  project.version '0.1.0'
+  
+  package :jar
+  
+  task :run => :compile do
+    system 'java -cp target/classes org.apache.killer.Main'
+  end
+end
+{% endhighlight %}
+
+Now, we can invoke @run@ exactly the way we want, with a minimum of wasted characters:
+
+{% highlight sh %}
+$ buildr run
+{% endhighlight %}
+
+
+h2(#summary). Summary
+
+As long as this guide was, we have barely even scratched the surface of Buildr's true power.  This was meant only to get you up and running as quickly as possible, exploiting some of Buildr's unique features to ease your build process.  For more comprehensive documentation, start reading about "projects in Buildr":projects.html and work your way from there.

data/doc/scripts/install-linux.sh

@@ -16,6 +16,7 @@
 if [ -z `which ruby` ] ; then
   echo "You do not have Ruby 1.8.6 ..."
   # yum comes first since some people have apt-get installed in addition to yum.
+  # urpmi is added in case of mandriva : apt-get or yum are working for mandriva too
   if [ `which yum` ] ; then
     echo "Installing Ruby using yum"
     sudo yum install ruby rubygems ruby-devel gcc
@@ -24,7 +25,7 @@ if [ -z `which ruby` ] ; then
     # ruby package does not contain RDoc, IRB, etc; ruby-full is a meta-package.
     # build-essentials not installed by default in Ubuntu, required for C extensions.
     sudo apt-get install ruby-full ruby1.8-dev libopenssl-ruby build-essential 
-    # RubyGems broken on Ubunutu, installing directly from source.
+    # RubyGems broken on Ubuntu, installing directly from source.
     echo "Installing RubyGems from RubyForge"
     wget http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz
     tar xzf rubygems-1.3.1.tgz
@@ -34,8 +35,15 @@ if [ -z `which ruby` ] ; then
     rm -rf rubygems-1.3.1
     # ruby is same as ruby1.8, we need gem that is same as gem1.8
     sudo ln -s /usr/bin/gem1.8 /usr/bin/gem
+  elif [ `which urpmi` ] ; then
+    echo "Installing Ruby using urpmi"
+    sudo urpmi ruby rubygems ruby-devel gcc
+    if [ $? -ne 0 ] ; then
+      echo "URPMI install error"
+      exit 1
+    fi
   else
-    echo "Can only install Ruby 1.8.6 using apt-get or yum, and can't find either one"
+    echo "Can only install Ruby 1.8.6 using apt-get, yum or urpmi, and can't find any of them"
     exit 1
   fi
   echo

data/doc/settings_profiles.textile

@@ -10,30 +10,24 @@ Buildr uses several environment variables that help you control how it works. So
 
 For example:
 
-<notextile>
 {% highlight sh %}
 $ export HTTP_PROXY=http://myproxy:8080
 {% endhighlight %}
-</notextile>
 
 There are other environment variables you will want to set when running Buildr, for example, to do a full build without running the tests:
 
-<notextile>
 {% highlight sh %}
 $ buildr test=no
 {% endhighlight %}
-</notextile>
 
-For convenience, when you set environment variables on the command line, the variable name is case insensitive, you can use either @test=no@ or @TEST=no@. Any other way (@export@, @ENV@, etc) the variable names are case sensitive.
+For convenience, the environment variables @TEST@ and @DEBUG@ are case insensitive, you can use either @test=no@ or @TEST=no@. Any other environment variable names are case sensitive.
 
 You can also set environment variables from within your Buildfile.  For example, if you discover that building your project requires gobs of JVM heap space, and you want all other team members to run with the same settings:
 
-<notextile>
 {% highlight ruby %}
 # This project builds a lot of code.
 ENV['JAVA_OPTS'] ||= '-Xms1g -Xmx1g'
 {% endhighlight %}
-</notextile>
 
 Make sure to set any environment variables at the very top of the Buildfile, above any Ruby statement (even @require@).
 
@@ -58,12 +52,10 @@ p(note). Buildr does not check any of the arguments in @JAVA_OPTS@.  A common mi
 
 Some extensions may use additional environment variables, and of course, you can always add your own.  This example uses two environment variables for specifying the username and password:
 
-<notextile>
 {% highlight ruby %}
 repositories.upload_to[:username] = ENV['USERNAME']
 repositories.upload_to[:password] = ENV['PASSWORD']
 {% endhighlight %}
-</notextile>
 
 
 h2(#personal). Personal Settings
@@ -76,7 +68,6 @@ The prefered way to store personal settings is to create a @.buildr/settings.yam
 
 Here's an example @settings.yaml@:
 
-<notextile>
 {% highlight yaml %}
 # The repositories hash is read automatically by buildr.
 repositories:
@@ -101,11 +92,9 @@ im:
   usr: notifier@company-jabber.com
   pwd: secret
 {% endhighlight %}
-</notextile>
 
 Later your buildfile or addons can reference user preferences using the  hash returned by the @Buildr.settings.user@ accessor.
 
-<notextile>
 {% highlight ruby %}
 task 'relase-notification' do
  usr, pwd, server = settings.user['im'].values_at('usr', 'pwd', 'server')
@@ -113,7 +102,6 @@ task 'relase-notification' do
  jabber.msg("We are pleased to announce the last stable version #{VERSION}")
 end
 {% endhighlight %}
-</notextile>
 
 
 h2(#build). Build Settings
@@ -122,7 +110,6 @@ Build settings are local to the project being built, and are placed in the @buil
 
 They help keep the buildfile and build.yaml file simple and readable, working to the advantages of each one.  Example for build settings are gems, repositories and artifacts used by that build.
 
-<notextile>
 {% highlight yaml %}
 # This project requires the following ruby gems, buildr addons
 gems: 
@@ -151,24 +138,20 @@ twitter:
 jira: 
   uri: https://jira.corp.org
 {% endhighlight %}
-</notextile>
 
 When buildr is loaded, required ruby gems will be installed if needed, thus adding features like the imaginary twitter notifier addon.
 
 Artifacts defined on @build.yaml@ can be referenced on your buildfile by supplying the ruby symbol to the @Buildr.artifact@ and @Buildr.artifacts@ methods.  The @compile.with@, @test.with@ methods can also be given these names.
 
-<notextile>
 {% highlight ruby %}
 define 'my_project' do 
   compile.with artifacts(:log4j, :j2ee)
   test.with :spring, :j2ee
 end
 {% endhighlight %}
-</notextile>
 
 Build settings can be retreived using the @Buildr.settings.build@ accessor.
 
-<notextile>
 {% highlight ruby %}
  task 'create_patch' do 
    patch = Git.create_patch :interactive => true
@@ -178,7 +161,6 @@ Build settings can be retreived using the @Buildr.settings.build@ accessor.
    end
  end
 {% endhighlight %}
-</notextile>
 
 
 h2(#variable). Non constant settings
@@ -189,7 +171,6 @@ The loading order allows you to place global settings that affect all your build
 
 Here's an example @buildr.rb@:
 
-<notextile>
 {% highlight ruby %}
 # Only I should know that
 repositories.upload_to[:username] = 'assaf'
@@ -197,7 +178,6 @@ repositories.upload_to[:password] = 'supersecret'
 # Search here first, it's faster
 repositories.remote << 'http://inside-the-firewall'
 {% endhighlight %}
-</notextile> 
 
 
 h2(#environments). Environments
@@ -206,35 +186,29 @@ One common use case is adapting the build to different environments.  For exampl
 
 So let's start by talking about the build environment.  Buildr has a global attributes that indicates which environment it's running in, accessible from the @environment@ method.  You can set the current build environment in one of two ways.  Using the @-e/--environment@ command line option:
 
-<notextile>
 {% highlight sh %}
 $ buildr -e test
 (in /home/john/project, test)
 {% endhighlight %}
-</notextile>
 
 Or by setting the environment variable @BUILDR_ENV@:
 
-<notextile>
 {% highlight text %}
 $ export BUILDR_ENV=production
 $ buildr
 (in /home/john/project, production)
 {% endhighlight %}
-</notextile>
 
 Unless you tell it otherwise, Buildr assumes you're developing and sets the environment to @development@.
 
 Here's a simple example for handling different environments within the Buildfile:
 
-<notextile>
 {% highlight ruby %}
 project 'db-module' do
   db = (environment == 'production' ? 'oracle' : 'hsql')
   resources.from(_("src/main/#{db}"))
 end
 {% endhighlight %}
-</notextile>
 
 We recommend picking a convention for your different environments and following it across all your projects.  For example:
 
@@ -252,7 +226,6 @@ The profiles file is a YAML file called @profiles.yaml@ that you place in the sa
 
 For example, to support three different database configurations, we could write:
 
-<notextile>
 {% highlight yaml %}
 # HSQL, don't bother storing to disk.
 development:
@@ -269,11 +242,9 @@ production:
   db: oracle
   jdbc: oracle:thin:@bigstrong:1521:mighty
 {% endhighlight %}
-</notextile>
 
 Here's a simple example for a buildfile that uses the profile information:
 
-<notextile>
 {% highlight ruby %}
 project 'db-module' do
   # Copy SQL files specific for the database we're using,
@@ -283,7 +254,6 @@ project 'db-module' do
   resources.filter.using :jdbc=>Buildr.settings.profile['jdbc']
 end
 {% endhighlight %}
-</notextile>
 
 The @profile@ method returns the current profile, selected based on the current "environment":#environments.  You can get a list of all profiles by calling @profiles@.
 
@@ -293,7 +263,6 @@ We recommend following conventions and using the same environments in all your p
 
 YAML allows you to use anchors (@&@), similar to ID attributes in XML, reference the anchored element (@*@) elsewhere, and merge one element into another (@<<@).  For example:
 
-<notextile>
 {% highlight yaml %}
 # We'll reference this one as common.
 development: &common
@@ -306,7 +275,6 @@ test:
   <<: *common
   jdbc: hsqldb:file:testdb
 {% endhighlight %}
-</notextile>
 
 
 You can "learn more about YAML here":http://www.yaml.org, and use this handy "YAML quick reference":http://www.yaml.org/refcard.html.