buildr 1.3.3 → 1.3.4

data/doc/css/default.css

@@ -18,10 +18,9 @@
 body {
   background-color: #fff;
   color: #000;
-  font-family: "DejaVu Sans", Verdana, Helvetica;
+  font-family: "Helvetica Neue", "DejaVu Sans", "Verdana";
   text-align: center;
   line-height: 150%;
-  font-size: 12pt;
 }
 
 a:link, a:visited{
@@ -38,18 +37,20 @@ img {
 }
 
 pre, code {
-  font-family: "DejaVu Sans Mono", "Courier New", "Courier";
+  font-family: "Monaco", "DejaVu Sans Mono", "Courier New", "Courier";
   font-size: 11pt;
 }
 pre {
   margin: 0.3em 0 0.3em 0.9em;
   padding: 0;
-  line-height: 135%;
+  line-height: 1.8em;
   white-space: pre-wrap;       /* css-3 */
   white-space: -moz-pre-wrap !important;  /* Mozilla, since 1999 */
 }
+pre br { display: none; }
 
 h1, h2, h3 {
+  font-family: "Gill Sans";
   padding: 0;
   margin: 1.6em 0 0.6em -0.9em;
   line-height: 1.25em;
@@ -137,7 +138,7 @@ th, thead td {
   float: left;
   text-align: left;
   margin-right: 2em;
-  font-family: "DejaVu Sans", Verdana, Helvetica;
+  font-family: "Gill Sans";
   font-size: 11pt;
   text-align: right;
   border-right: 1px solid #ccc;

data/doc/css/print.css

@@ -18,7 +18,7 @@
 @page { 
   margin: 1in 0.75in 1in 0.75in;
   @top-left, @top-right {
-    font-family: "Gill Sans", "DejaVu Sans", Verdana, Helvetica;
+    font-family: "Gill Sans";
     font-weight: normal;
   }
 }
@@ -39,8 +39,7 @@
   title { string-set: doctitle content(); }
 
   body {
-    font-family: "Palatino", "DejaVu Serif", Helvetica;
-    font-size: 12pt;
+    font-family: "Helvetica Neue", "DejaVu Sans", "Verdana";
     margin: 0;
     color: black;
     background: white;
@@ -51,8 +50,8 @@
     page-break-before: always;
   }
   h1:first-child { page-break-before: avoid; }
-  h1, h2, h3, ol.toc {
-    font-family: "Gill Sans", "Courier", "DejaVu Sans", Verdana, Helvetica;
+  h1, h2, h3 {
+    font-family: "Gill Sans";
   }
   pre, p, blockquote { page-break-inside: avoid; }
   pre, code {
@@ -63,7 +62,9 @@
     background: transparent;
     text-decoration: none;
   }
-  #wrap, #content, #footer {
+
+  #header, #pages, #footer { display: none }
+  #wrap, #content {
     float: none !important;
     color: black;
     background: transparent;
@@ -73,28 +74,20 @@
     border: 0;
   }
 
-  #header {
-    margin-bottom: 5%;
-    font-size: 120%;
-  }
-  #header img { width: 4in; }
-  #header .tagline {
-    float: none !important;
-    position: static !important;
-    font-size: 1.2em;
-    text-align: center;
-  }
-
-  #pages, .noprint { display: none; }
-
   ol.toc a:link, ol.toc a:visited { text-decoration: none; }
   ol.toc a:after { content: leader('.') target-counter(attr(href), page); }
 
-  #footer { margin-top: 5%; }
-
-  #license {
+  .title {
+    page-break-before: always;
+    border: none;
+  }
+  .title img {
+    width: 20em;
+    margin: 2em auto 2em auto;
+  }
+  p.preface {
     page-break-before: always;
-    padding-top: 1in;
+    padding-top: 2.5in;
   }
 
 }

data/doc/css/syntax.css

@@ -14,39 +14,10 @@
  * under the License.
  */
 
-
-.ruby .normal   {}
-.ruby .comment  { color: gray; }
-.ruby .method   { color: lightblue; }
-.ruby .punct    {  color: darkblue; }
-.ruby .keyword, .ruby .symbol   { color: blue; }
-.ruby .string, .ruby .regex { color: green; }
-.ruby .char     { }
-.ruby .ident    { color: black; }
-.ruby .constant, ruby .class, ruby .module { color: darkblue; }
-.ruby .number   { color: blue; }
-.ruby .attribute { }
-.ruby .global   { }
-.ruby .expr     { }
-.ruby .escape   { }
-
-.xml .normal    {}
-.xml .namespace { color: darkblue; }
-.xml .tag       { color: blue; }
-.xml .comment   { color: gray; }
-.xml .punct     { color: darkblue; }
-.xml .string    { }
-.xml .number    { }
-.xml .attribute { color: blue; }
-
-.yaml .document { }
-.yaml .type     { }
-.yaml .key      { color: blue; }
-.yaml .comment  { color: gray; }
-.yaml .punct    { color: darkblue; }
-.yaml .string   { }
-.yaml .number   { }
-.yaml .time     { }
-.yaml .date     { }
-.yaml .ref      { color: green; }
-.yaml .anchor   { color: green; }
+.highlight .k, .highlight .kp { color: blue } /* keyword */
+.highlight .no { color: darkblue } /* constant */
+.highlight .s1 { color: green } /* string */
+.highlight .n { color: black } /* identifier */
+.highlight .o, .highlight .p { color: darkblue } /* = + */
+.highlight .ss { color: darkblue } /* symbol */
+.highlight .c1 { color: gray } /* comment */

data/doc/download.textile

@@ -0,0 +1,78 @@
+---
+layout: default
+title: Download
+---
+
+
+h2(#install).  Installing Buildr
+
+*The easy way:*  The "Getting Started guide":getting_started.html will show you how to install Buildr in a matter of minutes.
+
+
+h2(#dists).  Official & Unofficial Distributions
+
+The official Apache distribution consists of the digitally signed binaries (gems) and source packages "available below":#dist.  To install these binaries, you must first download them to disk and then install them using the @gem install@ command (or @rake install@ for a source distribution).
+
+In addition, contributors to this project maintain a separate distribution over on "RubyForge":http://rubyforge.org/projects/buildr.  Using this distribution, you're able to install Buildr directly from the remote gem repository and to automatically upgrade when a new release comes out.  The RubyForge distribution is *not* an official Apache distribution.
+
+The source code is included in both source and binary distribution, the Gem distribution expands the source code into your local Gem repository. That's in addition to getting the source code directly from "SVN":http://svn.apache.org/repos/asf/buildr or "GitHub":http://github.com/buildr/buildr/tree/master. Learn more about working with source code and "living on the edge":contributing.html#edge.
+
+
+h2(#dist).  Binaries and Source Code
+
+h3. buildr 1.3.4 (2009-04-21)
+
+|_. Package |_. MD5 Checksum |_. PGP |
+| "buildr-1.3.4-java.gem":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4-java.gem | "44ed67bf835cf2abdc2b6723b5eceadb":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4-java.gem.md5 | "Sig":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4-java.gem.asc |
+| "buildr-1.3.4.tgz":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.tgz | "7d918b88a3bb8139f28f6ff0b39d003c":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.tgz.md5 | "Sig":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.tgz.asc |
+| "buildr-1.3.4.zip":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.zip | "8f4cf84dc6e293aac5fba7e2a9cc0776":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.zip.md5 | "Sig":http://www.apache.org/dist/buildr/1.3.4/buildr-1.3.4.zip.asc |
+
+p>. ("Release signing keys":http://www.apache.org/dist/buildr/1.3.4/KEYS)
+
+
+h3. buildr 1.3.3-incubating (2008-10-08)
+
+|_. Package |_. MD5 Checksum |_. PGP |
+| "buildr-1.3.3-incubating.gem":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.gem | "7192dad45441630cbf07b85af5f9069a":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.gem.asc |
+| "buildr-1.3.3-java-incubating.gem":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-java-incubating.gem | "71ad4f0f8bfa951fa129db67a06b608a":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-java-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-java-incubating.gem.asc |
+| "buildr-1.3.3-incubating.tgz":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.tgz | "e5ee6fe5b86386520c91a9633d02814b":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.tgz.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.tgz.asc |
+| "buildr-1.3.3-incubating.zip":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.zip | "baab601fd46a877ee8e408891d68c842":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.zip.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.3-incubating/buildr-1.3.3-incubating.zip.asc |
+
+p>. ("Release signing keys":http://archive.apache.org/dist/buildr/1.3.3-incubating/KEYS)
+
+
+h3. buildr 1.3.2-incubating (2008-07-18)
+
+|_. Package |_. MD5 Checksum |_. PGP |
+| "buildr-1.3.2-incubating.gem":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.gem | "225504bc195334c4eb9d6dec814d9db1":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.gem.asc |
+| "buildr-1.3.2-java-incubating.gem":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-java-incubating.gem | "d7d8394c7aed887987be0e813e1e4cee":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-java-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-java-incubating.gem.asc |
+| "buildr-1.3.2-incubating.tgz":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.tgz | "611e97df1bc76382ecbe6b60e9340f2b":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.tgz.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.tgz.asc |
+| "buildr-1.3.2-incubating.zip":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.zip | "d65d20005f603338c0aedd4f17d0bc90":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.zip.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.2-incubating/buildr-1.3.2-incubating.zip.asc |
+
+p>. ("Release signing keys":http://archive.apache.org/dist/buildr/1.3.2-incubating/KEYS)
+
+
+
+h3. buildr 1.3.1-incubating (2008-05-19)
+
+|_. Package |_. MD5 Checksum |_. PGP |
+| "buildr-1.3.1-incubating.gem":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.gem | "476436429b9a6c4ed178009ba17dd724":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.gem.asc |
+| "buildr-1.3.1-java-incubating.gem":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-java-incubating.gem | "7af37acc10621b18d4b870119c36d998":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-java-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-java-incubating.gem.asc |
+| "buildr-1.3.1-incubating.tgz":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.tgz | "ad6694416fc2e6eb22ab1042dcc41411":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.tgz.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.tgz.asc |
+| "buildr-1.3.1-incubating.zip":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.zip | "0470349978b93e645ca2e9607e304ed1":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.zip.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.1-incubating/buildr-1.3.1-incubating.zip.asc |
+
+p>. ("Release signing keys":http://archive.apache.org/dist/buildr/1.3.1-incubating/KEYS)
+
+
+h3. buildr 1.3.0-incubating (2008-05-01)
+
+|_. Package |_. MD5 Checksum |_. PGP |
+| "buildr-1.3.0-incubating.gem":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.gem | "37758d0a8dabc570799b0a58d23d19f0":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.gem.asc |
+| "buildr-1.3.0-java-incubating.gem":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-java-incubating.gem | "6a3a86740077f739c111514e0e2b9e06":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-java-incubating.gem.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-java-incubating.gem.asc |
+| "buildr-1.3.0-incubating.tgz":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.tgz | "acd84ad8c5031962e65b0036f3bc2e76":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.tgz.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.tgz.asc |
+| "buildr-1.3.0-incubating.zip":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.zip | "d85945f05efd0e512e6d769e3dd1cc98":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.zip.md5 | "Sig":http://archive.apache.org/dist/buildr/1.3.0-incubating/buildr-1.3.0-incubating.zip.asc |
+
+p>. ("Release signing keys":http://archive.apache.org/dist/buildr/1.3.0-incubating/KEYS)
+
+
+p(note). When downloading from files please check the "md5sum":http://www.apache.org/dev/release-signing#md5 and verify the "OpenPGP":http://www.apache.org/dev/release-signing#openpgp compatible signature from the main Apache site. This "KEYS":http://archive.apache.org/dist/buildr/KEYS file contains the public keys used for signing releases. It is recommended that (when possible) a web of trust is used to confirm the identity of these keys. For more information, please see the "Apache Release FAQ":http://www.apache.org/dev/release.html.

data/doc/{pages/extending.textile → extending.textile}

@@ -1,6 +1,9 @@
-h1. Extending Buildr
+---
+layout: default
+title: Extending Buildr
+---
 
-h2. Organizing Tasks
+h2(#tasks). Organizing Tasks
 
 A couple of things we learned while working on Buildr.  Being able to write your own Rake tasks is a very powerful feature.  But if you find yourself doing the same thing over and over, you might also want to consider functions. They give you a lot more power and easy abstractions.
 
@@ -8,7 +11,8 @@ For example, we use OpenJPA in several projects.  It's a very short task, but ea
 
 Compare this:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 file('derby.sql') do
   REQUIRES = [
     'org.apache.openjpa:openjpa-all:jar:0.9.7-incubating',
@@ -21,23 +25,26 @@ file('derby.sql') do
       :classpath=>REQUIRES.join(File::PATH_SEPARATOR)
     ant.mapping :schemaAction=>'build', :sqlFile=>task.name,
       :ignoreErrors=>true do
-        ant.config :propertiesFile=>_(:source, :main, :sql, 'derby.xml')
+        ant.config :propertiesFile=>_('src/main/sql/derby.xml')
         ant.classpath :path=>projects('store', 'utils' ).
           flatten.map(&:to_s).join(File::PATH_SEPARATOR)
     end
   end
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 To this:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 file('derby.sql') do
   mapping_tool :action=>'build', :sql=>task.name,
-    :properties=>_(:source, :main, :sql, 'derby.xml'),
+    :properties=>_('src/main/sql/derby.xml'),
     :classpath=>projects('store', 'utils')
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 I prefer the second.  It's easier to look at the Buildfile and understand what it does.  It's easier to maintain when you only have to look at the important information.
 
@@ -48,25 +55,29 @@ If you want to share these pre-canned definitions between projects, you have a f
 For individual task files, you can also use "Sake":http://errtheblog.com/post/6069 for system-wide Rake tasks deployment.
 
 
-h2.  Creating Extensions
+h2(#extensions).  Creating Extensions
 
 The basic mechanism for extending projects in Buildr are Ruby modules.  In fact, base features like compiling and testing are all developed in the form of modules, and then added to the core Project class.
   
 A module defines instance methods that are then mixed into the project and become instance methods of the project.  There are two general ways for extending projects.  You can extend all projects by including the module in Project:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 class Project
   include MyExtension
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 You can also extend a given project instance and only that instance by extending it with the module:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 define 'foo' do
   extend MyExtension
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 Some extensions require tighter integration with the project, specifically for setting up tasks and properties, or for configuring tasks based on the project definition.  You can do that by adding callbacks to the process.
 
@@ -79,7 +90,8 @@ The easiest way to add callbacks is by incorporating the Extension module in you
 
 This example illustrates how to write a simple extension:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 module LinesOfCode
   include Extension
 
@@ -114,35 +126,42 @@ end
 class Buildr::Project
   include LinesOfCode
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 
-h2.  Using Alternative Layouts
+h2(#layouts).  Using Alternative Layouts
 
 Buildr follows a common convention for project layouts: Java source files appear in @src/main/java@ and compile to @target/classes@, resources are copied over from @src/main/resources@ and so forth.  Not all projects follow this convention, so it's now possible to specify an alternative project layout.
 
 The default layout is available in @Layout.default@, and all projects inherit it.  You can set @Layout.default@ to your own layout, or define a project with a given layout (recommended) by setting the @:layout@ property.  Projects inherit the layout from their parent projects.  For example:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 define 'foo', :layout=>my_layout do
   ...
 end
-}}}
+{% endhighlight %}
+</notextile>
 
 A layout is an object that implements the @expand@ method.  The easiest way to define a custom layout is to create a new @Layout@ object and specify mapping between names used by Buildr and actual paths within the project.  For example:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 my_layout = Layout.new
 my_layout[:source, :main, :java] = 'java'
 my_layout[:source, :main, :resources] = 'resources'
-}}}
+{% endhighlight %}
+</notextile>
 
 Partial expansion also works, so you can specify the above layout using:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 my_layout = Layout.new
 my_layout[:source, :main] = ''
-}}}
+{% endhighlight %}
+</notextile>
 
 If you need anything more complex, you can always subclass @Layout@ and add special handling in the @expand@ method, you'll find one such example in the API documentation.
 
@@ -158,7 +177,8 @@ The built-in tasks expand lists of symbols into relative paths, using the follow
 
 All tasks are encouraged to use the same convention, and whenever possible, we recommend using the project's @path_to@ method to expand a list of symbols into a path, or use the appropriate path when available.  For example:
 
-{{{!ruby
+<notextile>
+{% highlight ruby %}
 define 'bad' do
   # This may not be the real target.
   puts 'Compiling to ' + path_to('target/classes')
@@ -172,4 +192,5 @@ define 'good' do
   # This will work with different layouts.
   package(:jar).include path_to(:source, :main, :etc, '*')
 end
-}}}
+{% endhighlight %}
+</notextile>

data/doc/{pages/getting_started.textile → getting_started.textile}

@@ -1,143 +1,194 @@
-h1. Getting Started
+---
+layout: default
+title: Getting Started
+---
 
-h2.  Installing Buildr
 
-The installation instructions are slightly different for each operating system. Pick the one that best matches your operating system and target platform.
+*The easy way:*  We recommend you pick the platform you want to run Buildr on and then follow the _easy way_ instructions for that platform.  It could save you an hour or two struggling to install all the right dependencies.
 
-The @gem install@ and @gem update@ commands install Buildr from a binary distribution provided through "RubyForge":http://rubyforge.org/projects/buildr. This distribution is maintained by contributors to this project, but is *not* an official Apache distribution.  You can obtain the official Apache distribution files from the "download page":download.html.
+"Installing Buildr for JRuby":#jruby is the same on all operating systems.  Choose JRuby if you're working with Java 6 on OS X, developing with multiple JDKs, or just like JRuby better.
 
-The current release of Buildr for Ruby may not work well with Java 6, only Java 1.5 or earlier.  If you need to use Java 6, consider "Buildr for JRuby":#jruby.
+If you are running behind a proxy server, make sure the environment variable @HTTP_PROXY@ is set, as many of these steps require HTTP access.
 
+<br>
 
-h3.  Linux
+*In details:* The @gem install@ and @gem update@ commands install Buildr from a binary distribution provided through "RubyForge":http://rubyforge.org/projects/buildr. This distribution is maintained by contributors to this project, but is *not* an official Apache distribution.  You can obtain the official Apache distribution files from the "download page":download.html.
 
-To get started you will need a recent version of Ruby, Ruby Gems and build tools for compiling native libraries (@make@, @gcc@ and standard headers).
+Older versions of RubyGems are all kind of fail.  You want to avoid these unless you have the patience to install each Buildr dependency manually.  Get RubyGems 1.3.1 or later, and when using Debian packages (e.g. Ubuntu), make sure to get the unmolested RubyGems straight form the source.
+
+The Ruby interpreter and JVM must use compatible architectures.  For example, OS X comes with 32-bit version of Ruby, Java 1.5 in both 32-bit and 64-bit flavors, and 64-bit Java 6.  As a result you can run Ruby with Java 1.5 (32-bit), but to use Java 6 you either need to build Ruby from source for 64-bit, or use "Buildr for JRuby":#jruby.
+
+h2(#linux).  Installing on Linux
+
+*The easy way:* Use this bash script to "install Buildr on Linux":scripts/install-linux.sh.  This script will install the most recent version of Buildr, or if already installed, upgrade to the most recent version.  It will also install Ruby 1.8.6 if not already installed (requires @apt-get@ or @yum@) and upgrade to RubyGems 1.3.1 or later.
+
+p(note). At this time, the native Ruby-Java Bridge (RJB) does not work very well on Linux with JDK 1.6.  If you get Segmentation Fault errors with JDK 1.6, we recommend switching to JDK 1.5.
+
+<br>
+
+*In details:* To get started you will need a recent version of Ruby, Ruby Gems and build tools for compiling native libraries (@make@, @gcc@ and standard headers).
 
 On *RedHat/Fedora* you can use yum to install Ruby and RubyGems, and then upgrade to the most recent version of RubyGems:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo yum install ruby rubygems ruby-devel gcc
 $ sudo gem update --system
-}}}
+{% endhighlight %}
+</notextile>
 
 On *Ubuntu* you have to install several packages:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo apt-get install ruby-full ruby1.8-dev libopenssl-ruby build-essential 
-}}}
+{% endhighlight %}
+</notextile>
 
 The Debian package for @rubygems@ will not allow you to install Buildr, so you need to install RubyGems from source:
 
-{{{!sh
-$ wget http://rubyforge.org/frs/download.php/38646/rubygems-1.2.0.tgz 
-$ tar xzf rubygems-1.2.0.tgz
-$ cd rubygems-1.2.0
+<notextile>
+{% highlight sh %}
+$ wget http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz
+$ tar xzf rubygems-1.3.1.tgz
+$ cd rubygems-1.3.1
 $ sudo ruby setup.rb
 $ sudo ln -s /usr/bin/gem1.8 /usr/bin/gem
-}}}
+{% endhighlight %}
+</notextile>
 
 Before installing Buildr, please set the @JAVA_HOME@ environment variable to point to your JDK distribution.  Next, use Ruby Gem to install Buildr:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo env JAVA_HOME=$JAVA_HOME gem install buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 To upgrade to a new version or install a specific version:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo env JAVA_HOME=$JAVA_HOME gem update buildr
-$ sudo env JAVA_HOME=$JAVA_HOME gem install buildr -v 1.3.3
-}}}
+$ sudo env JAVA_HOME=$JAVA_HOME gem install buildr -v 1.3.4
+{% endhighlight %}
+</notextile>
+
+
+
+h2(#osx).  Installing on OS X
 
-You can also use this script "to install Buildr on Linux":scripts/install-linux.sh.  This script will install Buildr or if already installed, upgrade to a more recent version.  It will also install Ruby 1.8.6 if not already installed (using @yum@ or @apt-get@) and upgrage RubyGems to 1.0.1.
+*The easy way:* Use this script to "install Buildr on OS X":scripts/install-osx.sh.  This script will install the most recent version of Buildr, or if already installed, upgrade to the most recent version.  It will also install Ruby 1.8.6 if not already installed (using MacPorts/Fink) and upgrage RubyGems to 1.3.1 or later.
 
+<br>
 
-h3.  OS X
+*In details:* OS X 10.5 (Leopard) comes with a recent version of Ruby 1.8.6.  You do not need to install a different version of Ruby when running OS X 10.5.
 
-OS X 10.5 (Leopard) comes with a recent version of Ruby 1.8.6.  OS X 10.4 (Tiger) includes an older version of Ruby, we recommend you first install Ruby 1.8.6 using MacPorts (@sudo port install ruby rb-rubygems@), Fink or the "Ruby One-Click Installer for OS X":http://rubyosx.rubyforge.org/.
+OS X 10.4 (Tiger) includes an older version of Ruby that is not compatible with Buildr.  You can install Ruby 1.8.6 using MacPorts (@sudo port install ruby rb-rubygems@), Fink or the "Ruby One-Click Installer for OS X":http://rubyosx.rubyforge.org/.
 
 We recommend you first upgrade to the latest version of Ruby gems:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo gem update --system
-}}}
+{% endhighlight %}
+</notextile>
 
 Before installing Buildr, please set the @JAVA_HOME@ environment variable to point to your JDK distribution:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ export JAVA_HOME=/Library/Java/Home
-}}}
+{% endhighlight %}
+</notextile>
 
 To install Buildr:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo env JAVA_HOME=$JAVA_HOME gem install buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 To upgrade to a new version or install a specific version:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ sudo env JAVA_HOME=$JAVA_HOME gem update buildr
-$ sudo env JAVA_HOME=$JAVA_HOME gem install buildr -v 1.3.3
-}}}
+$ sudo env JAVA_HOME=$JAVA_HOME gem install buildr -v 1.3.4
+{% endhighlight %}
+</notextile>
 
-You can also use this script "to install Buildr on OS X":scripts/install-osx.sh.  This script will install Buildr or if already installed, upgrade to a more recent version.  It will also install Ruby 1.8.6 if not already installed (using MacPorts) and upgrage RubyGems to 1.0.1.
 
+h2(#windows).  Installing on Windows
 
-h3. Windows
+*The easy way:*  The easiest way to install Ruby is using the "one-click installer":http://rubyinstaller.rubyforge.org/.  Once installed, set the @JAVA_HOME@ environment variable and run @gem install buildr@.
 
-If you don't already have Ruby installed, now is the time to do it.  The easiest way to install Ruby is using the "one-click installer":http://rubyinstaller.rubyforge.org/.
+<br>
 
-We recommend you first upgrade to the latest version of Ruby gems:
+*In details:* We recommend you first upgrade to the latest version of Ruby gems:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 > gem update --system
-}}}
+{% endhighlight %}
+</notextile>
 
 Before installing Buildr, please set the @JAVA_HOME@ environment variable to point to your JDK distribution.  Next, use Ruby Gem to install Buildr:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 > gem install buildr
-}}}
-
-Buildr uses several libraries that include native extensions.  During installation it will ask you to pick a platform for these libraries.  By selecting @mswin32@ it will download and install pre-compiled DLLs for these extensions.
+{% endhighlight %}
+</notextile>
 
 To upgrade to a new version or install a specific version:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 > gem update buildr
-> gem install buildr -v 1.3.3
-}}}
+> gem install buildr -v 1.3.4
+{% endhighlight %}
+</notextile>
+
+
+h2(#jruby).  Installing for JRuby
 
+*The easy way:* Use this bash script to "install Buildr on JRuby":scripts/install-jruby.sh.  This script will install the most recent version of Buildr, or if already installed, upgrade to the most recent version.  If necessary, it will also install JRuby 1.1.6 in @/opt/jruby@ and update the @PATH@ variable in @~/.bash_profile@ or @~/.profile@.
 
-h3. JRuby
+<br>
 
-If you don't already have JRuby 1.1 or later installed, you can download it from the "JRuby site":http://dist.codehaus.org/jruby/.
+*In details:* If you don't already have JRuby 1.1.6 or later installed, you can download it from the "JRuby site":http://dist.codehaus.org/jruby/.
 
 After uncompressing JRuby, update your @PATH@ to include both @java@ and @jruby@ executables.
 
 For Linux and OS X:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ export PATH=$PATH:[path to JRuby]/bin:$JAVA_HOME/bin
 $ jruby -S gem install buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 For Windows:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 > set PATH=%PATH%;[path to JRuby]/bin;%JAVA_HOME%/bin
 > jruby -S gem install buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 To upgrade to a new version or install a specific version:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ jruby -S gem update buildr
-$ jruby -S gem install buildr -v 1.3.3
-}}}
+$ jruby -S gem install buildr -v 1.3.4
+{% endhighlight %}
+</notextile>
 
-You can also use this script "to install Buildr on JRuby":scripts/install-jruby.sh.  This script will install Buildr or if already installed, upgrade to a more recent version.  If necessary, it will also install JRuby 1.1 in @/opt/jruby@ and update the @PATH@ variable in @~/.bash_profile@ or @~/.profile@.
 
 *Important: Running JRuby and Ruby side by side*
 
@@ -149,59 +200,58 @@ To work exclusively with JRuby, make sure it shows first on the path, for exampl
 
 You can use JRuby and Ruby side by side, by running scripts with the @-S@ command line argument.  For example:
 
-{{{!
+<notextile>
+{% highlight sh %}
 $ # with Ruby
 $ ruby -S gem install buildr
 $ ruby -S buildr
 $ # with JRuby
 $ jruby -S gem install buildr
 $ jruby -S buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 Run @buildr --version@ from the command line to find which version of Buildr you are using by default.  If you see @(JRuby ...)@, Buildr is running on that version of JRuby.
 
 
-h2. Document Conventions
+h2(#conventions). Document Conventions
 
 Lines that start with @$@ are command lines, for example:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ # Run Buildr
 $ buildr
-}}}
+{% endhighlight %}
+</notextile>
 
 Lines that start with @=>@ show output from the console or the result of a method, for example:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 puts 'Hello world'
 => "Hello world"
-}}}
+{% endhighlight %}
+</notextile>
 
 And as you guessed, everything else is Buildfile Ruby or Java code.  You can figure out which language is which.
 
 
+h2(#running). Running Buildr
 
-h2. Running Buildr
-
-You need a *Buildfile*, a build script that tells Buildr all about the projects it's building, what they contain, what to produce, and so on.  The Buildfile resides in the root directory of your project.  We'll talk more about it in "the next chapter":projects.html.  If you don't already have one, ask Buildr to create it:
-
-{{{!sh
-$ buildr
-}}}
+You need a *Buildfile*, a build script that tells Buildr all about the projects it's building, what they contain, what to produce, and so on.  The Buildfile resides in the root directory of your project.  We'll talk more about it in "the next chapter":projects.html.  If you don't already have one, ask Buildr to create it by running @buildr@.
 
 p(tip). You'll notice that Buildr creates a file called @buildfile@.  It's case sensitive, but Buildr will look for either @buildfile@ or @Buildfile@.
 
 You use Buildr by running the @buildr@ command:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ buildr [options] [tasks] [name=value]
-}}}
-
-There are several options you can use, for a full list of options type:
+{% endhighlight %}
+</notextile>
 
-{{{!sh
-$ buildr --help
-}}}
+There are several options you can use, for a full list of options type @buildr --help@:
 
 |_. Option                  |_. Usage |
 | @-f/--buildfile [file]@   | Specify the buildfile.                                  |
@@ -216,51 +266,59 @@ $ buildr --help
 
 You can tell Buildr to run specific tasks and the order to run them.  For example:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 # Clean and rebuild
 buildr clean build
 # Package and install
 buildr install
-}}}
+{% endhighlight %}
+</notextile>
 
 If you don't specify a task, Buildr will run the "@build@ task":building.html, compiling source code and running test cases.  Running a task may run other tasks as well, for example, running the @install@ task will also run @package@.
 
-There are several "environment variables":settings_profiles.html#environment_variables that let you control how Buildr works, for example, to skip test cases during a build, or specify options for the JVM.  Depending on the variable, you may want to set it once in your environment, or set a different value each time you run Buildr.
+There are several "environment variables":settings_profiles.html#env_vars that let you control how Buildr works, for example, to skip test cases during a build, or specify options for the JVM.  Depending on the variable, you may want to set it once in your environment, or set a different value each time you run Buildr.
 
 For example:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ export JAVA_OPTS='-Xms1g -Xmx1g'
 $ buildr TEST=no
-}}}
+{% endhighlight %}
+</notextile>
 
 
-h2. Help Tasks
+h2(#help). Help Tasks
 
 Buildr includes a number of informative tasks.  Currently that number stands at two, but we'll be adding more tasks in future releases.  These tasks report information from the Buildfile, so you need one to run them.  For more general help (version number, command line arguments, etc) use @buildr --help@.
 
 To start with, type:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ buildr help
-}}}
+{% endhighlight %}
+</notextile>
 
 You can list the name and description of all your projects using the @help:projects@ task.  For example:
 
-{{{!sh
+<notextile>
+{% highlight sh %}
 $ buildr help:projects
 killer-app                 # Code. Build. ??? Profit!
 killer-app:teh-api         # Abstract classes and interfaces
 killer-app:teh-impl        # All those implementation details
 killer-app:la-web          # What our users see
-}}}
+{% endhighlight %}
+</notextile>
 
 You are, of course, describing your projects for the sake of those who will maintain your code, right?  To describe a project, or a task, call the @desc@ method before the project or task definition.
 
 So next let's talk about "projects":projects.html.
 
 
-h2. Learning More
+h2(#more). Learning More
 
 *Ruby*  It pays to pick up Ruby as a second (or first) programming language. It's fun, powerful and slightly addictive.  If you're interested in learning Ruby the language, a good place to start is "Programming Ruby: The Pragmatic Programmer's Guide":http://www.pragprog.com/titles/ruby/programming-ruby, fondly known as the _Pickaxe book_.