You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by do...@apache.org on 2013/10/06 09:17:12 UTC

svn commit: r1529576 [2/18] - in /buildr/site: ./ rdoc/ rdoc/Benchmark/ rdoc/Buildr/ rdoc/Buildr/ArchiveTask/ rdoc/Buildr/ArtifactNamespace/ rdoc/Buildr/Assets/ rdoc/Buildr/Checks/ rdoc/Buildr/Cobertura/ rdoc/Buildr/Cobertura/CoberturaExtension/ rdoc/B...

Modified: buildr/site/contributing.html
URL: http://svn.apache.org/viewvc/buildr/site/contributing.html?rev=1529576&r1=1529575&r2=1529576&view=diff
==============================================================================
--- buildr/site/contributing.html (original)
+++ buildr/site/contributing.html Sun Oct  6 07:17:05 2013
@@ -99,9 +99,7 @@
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>ruby --version
 <span class="nv">$ </span>buildr --version
 <span class="nv">$ </span>java --version
-</code></pre>
-</div>
-<h2 id="wiki">Community Wiki</h2>
+</code></pre></div><h2 id="wiki">Community Wiki</h2>
 <p><a href="http://cwiki.apache.org/confluence/display/BUILDR/Index">Our community Wiki</a>.</p>
 <h2 id="code">Contributing Code</h2>
 <p>Yes, please.</p>
@@ -123,17 +121,13 @@
 <h3 id="svn"><span class="caps">SVN</span></h3>
 <p>But if you want to work with the latest and greatest, you&#8217;ll want to check out <a href="http://svn.apache.org/repos/asf/buildr">Buildr from <span class="caps">SVN</span></a>:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>svn co http://svn.apache.org/repos/asf/buildr/trunk buildr
-</code></pre>
-</div>
-<p>You can also browse the <a href="http://svn.apache.org/repos/asf/buildr">Buildr repository</a>.</p>
+</code></pre></div><p>You can also browse the <a href="http://svn.apache.org/repos/asf/buildr">Buildr repository</a>.</p>
 <h3 id="git">Git</h3>
 <p>Not a fan of <span class="caps">SVN</span>?  We understand.  You can also use the <a href="http://git.apache.org">official Apache Git clone.</a>  This clone is maintained by the <span class="caps">ASF</span> and kept in sync with the <span class="caps">SVN</span> repository (though, in practice there may be some delay in cloning recent commits).  Apache&#8217;s Git hosting supports both git:// and http:// protocols (you should use git:// if at all possible as it is faster than http://):</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>git clone git://git.apache.org/buildr.git
 <span class="c"># or...</span>
 <span class="nv">$ </span>git clone http://git.apache.org/buildr.git
-</code></pre>
-</div>
-<p>If you want to learn more about Git, you can start by watching Scott Chacon’s <a href="http://en.oreilly.com/rails2008/public/asset/attachment/2816">Git presentation</a> (<span class="caps">PDF</span>), or any of the <a href="http://www.gitcasts.com/">Git screencasts</a>.  For more, there&#8217;s also the <a href="http://peepcode.com/products/git-internals-pdf">Git Internals book</a>.</p>
+</code></pre></div><p>If you want to learn more about Git, you can start by watching Scott Chacon’s <a href="http://en.oreilly.com/rails2008/public/asset/attachment/2816">Git presentation</a> (<span class="caps">PDF</span>), or any of the <a href="http://www.gitcasts.com/">Git screencasts</a>.  For more, there&#8217;s also the <a href="http://peepcode.com/products/git-internals-pdf">Git Internals book</a>.</p>
 <p>And keep this <a href="http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png">Git cheat sheet</a> close at hand. Very useful.</p>
 <h4>GitHub</h4>
 <p>You are also welcome to fork or clone the <a href="http://github.com/apache/buildr">Buildr repository on GitHub</a>.  This repository is just an exact mirror of the official Apache Git clone referenced above (updated every 30 minutes).  Some of the core committers also maintain their own forks of Buildr on GitHub, often containing experimental and in-progress development slated for eventual inclusion into the <span class="caps">SVN</span>.  For reference, they are listed below:</p>
@@ -146,28 +140,20 @@
 <p>To install Buildr from the source directory:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span><span class="nb">cd </span>buildr
 <span class="nv">$ </span>rake setup install
-</code></pre>
-</div>
-<p>When using Buildr for JRuby:</p>
+</code></pre></div><p>When using Buildr for JRuby:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span><span class="nb">cd </span>buildr
 <span class="nv">$ </span>jruby -S rake setup install
-</code></pre>
-</div>
-<p>The <em>setup</em> task takes care of installing all the necessary dependencies used for building, testing and running Buildr. Once in a while we upgrade or add new dependencies, if you&#8217;re experiencing a missing dependency, simply run <code>rake setup</code> again.</p>
+</code></pre></div><p>The <em>setup</em> task takes care of installing all the necessary dependencies used for building, testing and running Buildr. Once in a while we upgrade or add new dependencies, if you&#8217;re experiencing a missing dependency, simply run <code>rake setup</code> again.</p>
 <p>The <em>install</em> task creates a Gem in your working directory (<em>pkg/</em>) and install it in your local repository. Since Ruby Gems uses version numbers to detect new releases, if you installed Buildr this way and want to upgrade to the latest official release, you need to use <code>gem install buildr</code> rather than <code>gem upgrade</code>.</p>
 <p>Both <em>setup</em> and <em>install</em> tasks use the <code>sudo</code> command on platforms that require it (i.e. not Windows), so there&#8217;s no need to run <code>sudo rake</code> when working with the Buildr source code.</p>
 <h3>Using development build</h3>
 <p>Occasionally we&#8217;ll make development builds from the current code in trunk/head. We appreciate if you can take the time to test those out and report any bugs. To install development builds, use the Gem repository at <code>people.apache.org/~assaf/buildr/snapshot</code>:</p>
 <div class="highlight"><pre><code class="sh">gem <span class="nb">source</span> --add http://people.apache.org/~assaf/buildr/snapshot/
-</code></pre>
-</div>
-<p>Since Ruby Gems uses version numbers to detect new releases, if you installed Buildr from a snapshot and want to upgrade to a newer snapshot or the latest official release, you need to use <code>gem install buildr</code> rather than <code>gem upgrade</code>.</p>
+</code></pre></div><p>Since Ruby Gems uses version numbers to detect new releases, if you installed Buildr from a snapshot and want to upgrade to a newer snapshot or the latest official release, you need to use <code>gem install buildr</code> rather than <code>gem upgrade</code>.</p>
 <p>If you want to go back to using the RubyForge releases:</p>
 <div class="highlight"><pre><code class="sh">gem <span class="nb">source</span> --remove http://people.apache.org/~assaf/buildr/snapshot/
 gem install buildr
-</code></pre>
-</div>
-<h2 id="testing">Tested and Documented</h2>
+</code></pre></div><h2 id="testing">Tested and Documented</h2>
 <p>Two things we definitely encourage!</p>
 <h3>Testing/Specs</h3>
 <p>Obviously we won&#8217;t turn down patches, but we&#8217;ll love you even more if you include a test case.  One that will fail without the patch, and run successfully with it.  If not for our love, then think of the benefit to you: once we add that test case, we won&#8217;t accidentally break that feature in the next release.</p>
@@ -175,20 +161,14 @@ gem install buildr
 <p>You can run an individual specifications using the <code>spec</code> command, for example:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>spec spec/compiler_spec.rb
 <span class="nv">$ </span>spec spec/compiler_spec.rb -l 409
-</code></pre>
-</div>
-<p>The first command will run all the specifications in <code>compiler_spec</code>, the second command will run only the specification identified by line 409 of that file. You can use line numbers to point at a particular specification (lines starting with <code>it</code>), or set of specifications (lines starting with <code>describe</code>). You can also use the <code>-e</code> command line option to name a particular specification.</p>
+</code></pre></div><p>The first command will run all the specifications in <code>compiler_spec</code>, the second command will run only the specification identified by line 409 of that file. You can use line numbers to point at a particular specification (lines starting with <code>it</code>), or set of specifications (lines starting with <code>describe</code>). You can also use the <code>-e</code> command line option to name a particular specification.</p>
 <p>To make sure your change did not break anything else, you can run all the specifications (be patient, we have a lot of these):</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>rake spec
-</code></pre>
-</div>
-<p>If you get any failures, you can use <code>rake failed</code> to run only the failed specs, and repeat until there are no more failed specs to run. The list of failed specs is stored in the file <em>failed</em>.</p>
+</code></pre></div><p>If you get any failures, you can use <code>rake failed</code> to run only the failed specs, and repeat until there are no more failed specs to run. The list of failed specs is stored in the file <em>failed</em>.</p>
 <p>We always <code>rake spec</code> before making a release.</p>
 <p>For full test coverage:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>rake coverage
-</code></pre>
-</div>
-<p>Specification and coverage reports are <span class="caps">HTML</span> files you can view with a Web browser, look for them in the <em>reports</em> directory. You can also check out the <a href="specs.html">RSpec report</a> and <a href="coverage/index.html">test coverage</a> we publish with each release.</p>
+</code></pre></div><p>Specification and coverage reports are <span class="caps">HTML</span> files you can view with a Web browser, look for them in the <em>reports</em> directory. You can also check out the <a href="specs.html">RSpec report</a> and <a href="coverage/index.html">test coverage</a> we publish with each release.</p>
 <h2 id="docs">Documentation</h2>
 <p>Yes, we do make typos, spelling errors and sometimes we write things that don&#8217;t make sense, so if you find a documentation bug, or want to help make the documentation even better, here&#8217;s the way to do it.</p>
 <p>For simple typos and quick fixes, just send a message to the mailing list or log an issue in <span class="caps">JIRA</span>.</p>
@@ -214,15 +194,11 @@ end
 <p>To go from Textile to <span class="caps">HTML</span> we use <a href="http://github.com/mojombo/jekyll">Jekyll</a>.  You can use the <code>jekyll</code> rake task to transform the files under <code>doc</code> and create a copy of the Web site in the directory <code>_site</code>.  For example:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>rake jekyll
 <span class="nv">$ </span>open _site/index.html
-</code></pre>
-</div>
-<p>There is no live editing, but you can run <code>rake jekyll auto=true</code>, and when you update and save a Textile page it will regenerate the corresponding <span class="caps">HTML</span> page.</p>
+</code></pre></div><p>There is no live editing, but you can run <code>rake jekyll auto=true</code>, and when you update and save a Textile page it will regenerate the corresponding <span class="caps">HTML</span> page.</p>
 <p>To go from <span class="caps">HTML</span> to <span class="caps">PDF</span> we use <a href="http://www.princexml.com/">PrinceXML</a>.  The target file <code>buildr.pdf</code> is generated by first running Jekyll and then merging the generated <span class="caps">HTML</span> pages into a single <span class="caps">PDF</span> document.  For example:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>rake buildr.pdf
 <span class="nv">$ </span>open buildr.pdf
-</code></pre>
-</div>
-<h2 id="ci">Continuous Integration</h2>
+</code></pre></div><h2 id="ci">Continuous Integration</h2>
 <p>Buildr uses the Jenkins continuous integration tool to perform builds, run tests and report back on problems when changes are made to the source code repository.</p>
 <p>The care and feeding of the <a href="https://builds.apache.org/view/A-F/view/Buildr">CI Jobs</a> is the responsibility of the committers. To get access to configure the CI Jobs a committer needs to follow the directions on the <a href="http://wiki.apache.org/general/Hudson">jenkins</a> documentation site.</p>
 <p>You may also need to coordinate with the Apache infrastructure team to get accounts on the actual slave hosts that run the CI jobs. This access may be required to install tools and gems required to run the CI jobs. The main slave host to get access to is vesta.apache.org at the time of writing. You can also log on to the slave host, impersonate hudson and manually run tasks when you are attempting to track down build problems. Of course to impersonate hudson you will need to learn how to use <a href="http://apache.org/dev/freebsd-jails"><span class="caps">OPIE</span>.</a></p>
@@ -252,9 +228,7 @@ rvm install ruby-1.8.7-p358
 rvm install ruby-1.9.2-p320
 rvm install jruby-1.6.7
 rvm install ruby-1.9.3-p194
-</code></pre>
-</div>
-<p>It should also be noted that jruby-1.6.7 release has a native library that is compiled using a more modern version of libc than is available on this variant of the operating system. We could download the source release and recompile the library but instead we have just avoided the need for any use of the ruby native interface library in our CI infrastructure.</p>
+</code></pre></div><p>It should also be noted that jruby-1.6.7 release has a native library that is compiled using a more modern version of libc than is available on this variant of the operating system. We could download the source release and recompile the library but instead we have just avoided the need for any use of the ruby native interface library in our CI infrastructure.</p>
 <h3 id="ciwindows">Windows Setup</h3>
 <p>The ci infrastructure on the windows host (hudson-win.apache.org) is a little fragile. First you need to <span class="caps">RDP</span> in and download the support libraries. We have manually installed the tools in the following locations. Note: it is important to make the locations read-write access to the hudson user.</p>
 <div class="highlight"><pre><code class="sh">F:<span class="se">\h</span>udson<span class="se">\t</span>ools<span class="se">\R</span>uby193-p194
@@ -262,9 +236,7 @@ F:<span class="se">\h</span>udson<span c
 F:<span class="se">\h</span>udson<span class="se">\t</span>ools<span class="se">\R</span>uby187-p370
 F:<span class="se">\h</span>udson<span class="se">\t</span>ools<span class="se">\j</span>ruby-1.6.7
 F:<span class="se">\h</span>udson<span class="se">\t</span>ools<span class="se">\s</span>cala-2.9.0.1
-</code></pre>
-</div>
-<p><span class="caps">WARNING</span>: Several attempts were made to use GEM_HOME to install the dependent gems for each test in a separate location but we were unable to figure out the mechanisms via which sub-shells would inherit the paths and the ability to run tools such as rspec.</p>
+</code></pre></div><p><span class="caps">WARNING</span>: Several attempts were made to use GEM_HOME to install the dependent gems for each test in a separate location but we were unable to figure out the mechanisms via which sub-shells would inherit the paths and the ability to run tools such as rspec.</p>
 <h2 id="contributors">Contributors</h2>
 <p>Here is the list of people who are actively working and committing on Buildr:</p>
 <p><strong><a href="http://labnotes.org">Assaf Arkin</a></strong> (assaf at apache.org)</p>

Modified: buildr/site/download.html
URL: http://svn.apache.org/viewvc/buildr/site/download.html?rev=1529576&r1=1529575&r2=1529576&view=diff
==============================================================================
--- buildr/site/download.html (original)
+++ buildr/site/download.html Sun Oct  6 07:17:05 2013
@@ -88,6 +88,74 @@
 <p>In addition, contributors to this project maintain a separate distribution over on <a href="http://rubyforge.org/projects/buildr">RubyForge</a>.  Using this distribution, you&#8217;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 <strong>not</strong> an official Apache distribution.</p>
 <p>The source code is included in both source and binary distribution, the Gem distribution expands the source code into your local Gem repository. That&#8217;s in addition to getting the source code directly from <a href="http://svn.apache.org/repos/asf/buildr"><span class="caps">SVN</span></a> or <a href="http://github.com/buildr/buildr/tree/master">GitHub</a>. Learn more about working with source code and <a href="contributing.html#edge">living on the edge</a>.</p>
 <h2 id="dist">Binaries and Source Code</h2>
+<h3>buildr 1.4.13 (2013-10-02)</h3>
+<table>
+	<tr>
+		<th>Package </th>
+		<th>MD5 Checksum </th>
+		<th><span class="caps">PGP</span> </th>
+	</tr>
+	<tr>
+		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.13/buildr-1.4.13-java.gem">buildr-1.4.13-java.gem</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13-java.gem.md5">3081ffb091e562e27181b87e79054901</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13-java.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem">buildr-1.4.13-x86-mswin32.gem</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem.md5">8853d45386b50c0b6bef1a20f9ce0e1e</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.13/buildr-1.4.13.gem">buildr-1.4.13.gem</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.gem.md5">f7ef978a3604f583606c14e979f7d6b1</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.13/buildr-1.4.13.tgz">buildr-1.4.13.tgz</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.tgz.md5">933b601caecaad4ebcffd00311d4daa6</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.tgz.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.13/buildr-1.4.13.zip">buildr-1.4.13.zip</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.zip.md5">80bedc26b8a9597572fb8d563f1eeff0</a> </td>
+		<td> <a href="http://www.apache.org/dist/buildr/1.4.13/buildr-1.4.13.zip.asc">Sig</a> </td>
+	</tr>
+</table>
+<p style="text-align:right;">(<a href="http://www.apache.org/dist/buildr/1.4.13/KEYS">Release signing keys</a>)</p>
+<h3>buildr 1.4.13 (2013-10-02)</h3>
+<table>
+	<tr>
+		<th>Package </th>
+		<th>MD5 Checksum </th>
+		<th><span class="caps">PGP</span> </th>
+	</tr>
+	<tr>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-java.gem">buildr-1.4.13-java.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-java.gem.md5">ffcc5a2de357ca7bd6b1e0f9b6b03726</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-java.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem">buildr-1.4.13-x86-mswin32.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem.md5">8ddd577888adde3de0dfb446dd2ded20</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13-x86-mswin32.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.gem">buildr-1.4.13.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.gem.md5">b55c573116d8ea444c71c3eadff52c46</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.gem.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.tgz">buildr-1.4.13.tgz</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.tgz.md5">b3a4c8f22d56e043df8b7a7b862af0e0</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.tgz.asc">Sig</a> </td>
+	</tr>
+	<tr>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.zip">buildr-1.4.13.zip</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.zip.md5">58365ecd0fa7f3ec81d2009ffb045505</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.13/buildr-1.4.13.zip.asc">Sig</a> </td>
+	</tr>
+</table>
+<p style="text-align:right;">(<a href="http://archive.apache.org/dist/buildr/1.4.13/KEYS">Release signing keys</a>)</p>
 <h3>buildr 1.4.12 (2013-05-04)</h3>
 <table>
 	<tr>
@@ -96,32 +164,32 @@
 		<th><span class="caps">PGP</span> </th>
 	</tr>
 	<tr>
-		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.12/buildr-1.4.12-java.gem">buildr-1.4.12-java.gem</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12-java.gem.md5">c4e4587a6c908dd3036ef8df785a3428</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12-java.gem.asc">Sig</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-java.gem">buildr-1.4.12-java.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-java.gem.md5">c4e4587a6c908dd3036ef8df785a3428</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-java.gem.asc">Sig</a> </td>
 	</tr>
 	<tr>
-		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem">buildr-1.4.12-x86-mswin32.gem</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem.md5">afba0a6b9a41db270540eea611863a57</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem.asc">Sig</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem">buildr-1.4.12-x86-mswin32.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem.md5">afba0a6b9a41db270540eea611863a57</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12-x86-mswin32.gem.asc">Sig</a> </td>
 	</tr>
 	<tr>
-		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.12/buildr-1.4.12.gem">buildr-1.4.12.gem</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.gem.md5">6c2fe37ef05705d4419e0ba1922df658</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.gem.asc">Sig</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.gem">buildr-1.4.12.gem</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.gem.md5">6c2fe37ef05705d4419e0ba1922df658</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.gem.asc">Sig</a> </td>
 	</tr>
 	<tr>
-		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.12/buildr-1.4.12.tgz">buildr-1.4.12.tgz</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.tgz.md5">eda08e0ec89713d67a065a3c22110065</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.tgz.asc">Sig</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.tgz">buildr-1.4.12.tgz</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.tgz.md5">eda08e0ec89713d67a065a3c22110065</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.tgz.asc">Sig</a> </td>
 	</tr>
 	<tr>
-		<td> <a href="http://www.apache.org/dyn/closer.cgi/buildr/1.4.12/buildr-1.4.12.zip">buildr-1.4.12.zip</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.zip.md5">b23f65c57f0aa148044e7ce1b1718bca</a> </td>
-		<td> <a href="http://www.apache.org/dist/buildr/1.4.12/buildr-1.4.12.zip.asc">Sig</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.zip">buildr-1.4.12.zip</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.zip.md5">b23f65c57f0aa148044e7ce1b1718bca</a> </td>
+		<td> <a href="http://archive.apache.org/dist/buildr/1.4.12/buildr-1.4.12.zip.asc">Sig</a> </td>
 	</tr>
 </table>
-<p style="text-align:right;">(<a href="http://www.apache.org/dist/buildr/1.4.12/KEYS">Release signing keys</a>)</p>
+<p style="text-align:right;">(<a href="http://archive.apache.org/dist/buildr/1.4.12/KEYS">Release signing keys</a>)</p>
 <h3>buildr 1.4.11 (2013-03-14)</h3>
 <table>
 	<tr>

Modified: buildr/site/extending.html
URL: http://svn.apache.org/viewvc/buildr/site/extending.html?rev=1529576&r1=1529575&r2=1529576&view=diff
==============================================================================
--- buildr/site/extending.html (original)
+++ buildr/site/extending.html Sun Oct  6 07:17:05 2013
@@ -94,26 +94,22 @@
   <span class="n">ant</span><span class="p">(</span><span class="s1">&#39;openjpa&#39;</span><span class="p">)</span> <span class="k">do</span> <span class="o">|</span><span class="n">ant</span><span class="o">|</span>
     <span class="n">ant</span><span class="o">.</span><span class="n">taskdef</span> <span class="ss">:name</span><span class="o">=&gt;</span><span class="s1">&#39;mapping&#39;</span><span class="p">,</span>
       <span class="ss">:classname</span><span class="o">=&gt;</span><span class="s1">&#39;org.apache.openjpa.jdbc.ant.MappingToolTask&#39;</span><span class="p">,</span>
-      <span class="ss">:classpath</span><span class="o">=&gt;</span><span class="no">REQUIRES</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="no">File</span><span class="o">::</span><span class="no">PATH_SEPARATOR</span><span class="p">)</span>
+      <span class="ss">:classpath</span><span class="o">=&gt;</span><span class="no">REQUIRES</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="ss">File</span><span class="p">:</span><span class="ss">:PATH_SEPARATOR</span><span class="p">)</span>
     <span class="n">ant</span><span class="o">.</span><span class="n">mapping</span> <span class="ss">:schemaAction</span><span class="o">=&gt;</span><span class="s1">&#39;build&#39;</span><span class="p">,</span> <span class="ss">:sqlFile</span><span class="o">=&gt;</span><span class="n">task</span><span class="o">.</span><span class="n">name</span><span class="p">,</span>
       <span class="ss">:ignoreErrors</span><span class="o">=&gt;</span><span class="kp">true</span> <span class="k">do</span>
         <span class="n">ant</span><span class="o">.</span><span class="n">config</span> <span class="ss">:propertiesFile</span><span class="o">=&gt;</span><span class="n">_</span><span class="p">(</span><span class="s1">&#39;src/main/sql/derby.xml&#39;</span><span class="p">)</span>
         <span class="n">ant</span><span class="o">.</span><span class="n">classpath</span> <span class="ss">:path</span><span class="o">=&gt;</span><span class="n">projects</span><span class="p">(</span><span class="s1">&#39;store&#39;</span><span class="p">,</span> <span class="s1">&#39;utils&#39;</span> <span class="p">)</span><span class="o">.</span>
-          <span class="n">flatten</span><span class="o">.</span><span class="n">map</span><span class="p">(</span><span class="o">&amp;</span><span class="ss">:to_s</span><span class="p">)</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="no">File</span><span class="o">::</span><span class="no">PATH_SEPARATOR</span><span class="p">)</span>
+          <span class="n">flatten</span><span class="o">.</span><span class="n">map</span><span class="p">(</span><span class="o">&amp;</span><span class="ss">:to_s</span><span class="p">)</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="ss">File</span><span class="p">:</span><span class="ss">:PATH_SEPARATOR</span><span class="p">)</span>
     <span class="k">end</span>
   <span class="k">end</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>To this:</p>
+</code></pre></div><p>To this:</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">file</span><span class="p">(</span><span class="s1">&#39;derby.sql&#39;</span><span class="p">)</span> <span class="k">do</span>
   <span class="n">mapping_tool</span> <span class="ss">:action</span><span class="o">=&gt;</span><span class="s1">&#39;build&#39;</span><span class="p">,</span> <span class="ss">:sql</span><span class="o">=&gt;</span><span class="n">task</span><span class="o">.</span><span class="n">name</span><span class="p">,</span>
     <span class="ss">:properties</span><span class="o">=&gt;</span><span class="n">_</span><span class="p">(</span><span class="s1">&#39;src/main/sql/derby.xml&#39;</span><span class="p">),</span>
     <span class="ss">:classpath</span><span class="o">=&gt;</span><span class="n">projects</span><span class="p">(</span><span class="s1">&#39;store&#39;</span><span class="p">,</span> <span class="s1">&#39;utils&#39;</span><span class="p">)</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>I prefer the second.  It&#8217;s easier to look at the Buildfile and understand what it does.  It&#8217;s easier to maintain when you only have to look at the important information.</p>
+</code></pre></div><p>I prefer the second.  It&#8217;s easier to look at the Buildfile and understand what it does.  It&#8217;s easier to maintain when you only have to look at the important information.</p>
 <p>But just using functions is not always enough.  You end up with a Buildfile containing a lot of code that clearly doesn&#8217;t belong there.  For starters, I recommend putting it in the <code>tasks</code> directory.  Write it into a file with a <code>.rake</code> extension and place that in the <code>tasks</code> directory next to the Buildfile.  Buildr will automatically pick it up and load it for you.</p>
 <p>If you want to share these pre-canned definitions between projects, you have a few more options.  You can share the <code>tasks</code> directory using <span class="caps">SVN</span> externals, Git modules, or whichever cross-repository feature your source control system supports. Another mechanism with better version control is to package all these tasks, functions and modules into a <a href="http://rubygems.org/">Gem</a> and require it from your Buildfile.  You can run your own internal Gem server for that.</p>
 <p>To summarize, there are several common ways to distribute extensions:</p>
@@ -132,15 +128,11 @@
 <div class="highlight"><pre><code class="ruby"><span class="k">class</span> <span class="nc">Project</span>
   <span class="kp">include</span> <span class="no">MyExtension</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>You can also extend a given project instance and only that instance by extending it with the module:</p>
+</code></pre></div><p>You can also extend a given project instance and only that instance by extending it with the module:</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">define</span> <span class="s1">&#39;foo&#39;</span> <span class="k">do</span>
   <span class="kp">extend</span> <span class="no">MyExtension</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>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.</p>
+</code></pre></div><p>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.</p>
 <p>The easiest way to add callbacks is by incorporating the Extension module in your own extension, and using the various class methods to define callback behavior.</p>
 <table>
 	<tr>
@@ -202,9 +194,7 @@
 <span class="k">class</span> <span class="nc">Buildr</span><span class="o">::</span><span class="no">Project</span>
     <span class="kp">include</span> <span class="no">LinesOfCode</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>You may find interesting that this Extension <span class="caps">API</span> is used pervasively inside Buildr itself.  Many of the standard tasks such as <code>compile</code>, <code>test</code>, <code>package</code>  are extensions to a very small core.</p>
+</code></pre></div><p>You may find interesting that this Extension <span class="caps">API</span> is used pervasively inside Buildr itself.  Many of the standard tasks such as <code>compile</code>, <code>test</code>, <code>package</code>  are extensions to a very small core.</p>
 <p>Starting with Buildr 1.4, it&#8217;s possible to define ordering between <code>before_define</code> and <code>after_define</code> code blocks in a way similar to Rake&#8217;s dependencies.  For example, if you wanted to override <code>project.test.compile.from</code> in <code>after_define</code>, you could do so by in</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">after_define</span><span class="p">(</span><span class="ss">:functional_tests</span><span class="p">)</span> <span class="k">do</span> <span class="o">|</span><span class="n">project</span><span class="o">|</span>
   <span class="c1"># Change project.test.compile.from if it&#39;s not already pointing</span>
@@ -218,29 +208,21 @@
 <span class="c1"># make sure project.test.compile.from is updated before the</span>
 <span class="c1"># compile extension picks up its value</span>
 <span class="n">after_define</span><span class="p">(</span><span class="ss">:compile</span> <span class="o">=&gt;</span> <span class="ss">:functional_test</span><span class="p">)</span>
-</code></pre>
-</div>
-<p>Core extensions provide the following named callbacks: <code>compile</code>, <code>test</code>, <code>build</code>, <code>package</code> and <code>check</code>.</p>
+</code></pre></div><p>Core extensions provide the following named callbacks: <code>compile</code>, <code>test</code>, <code>build</code>, <code>package</code> and <code>check</code>.</p>
 <h2 id="layouts">Using Alternative Layouts</h2>
 <p>Buildr follows a common convention for project layouts: Java source files appear in <code>src/main/java</code> and compile to <code>target/classes</code>, resources are copied over from <code>src/main/resources</code> and so forth.  Not all projects follow this convention, so it&#8217;s now possible to specify an alternative project layout.</p>
 <p>The default layout is available in <code>Layout.default</code>, and all projects inherit it.  You can set <code>Layout.default</code> to your own layout, or define a project with a given layout (recommended) by setting the <code>:layout</code> property.  Projects inherit the layout from their parent projects.  For example:</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">define</span> <span class="s1">&#39;foo&#39;</span><span class="p">,</span> <span class="ss">:layout</span><span class="o">=&gt;</span><span class="n">my_layout</span> <span class="k">do</span>
   <span class="o">.</span><span class="n">.</span><span class="o">.</span>
 <span class="k">end</span>
-</code></pre>
-</div>
-<p>A layout is an object that implements the <code>expand</code> method.  The easiest way to define a custom layout is to create a new <code>Layout</code> object and specify mapping between names used by Buildr and actual paths within the project.  For example:</p>
+</code></pre></div><p>A layout is an object that implements the <code>expand</code> method.  The easiest way to define a custom layout is to create a new <code>Layout</code> object and specify mapping between names used by Buildr and actual paths within the project.  For example:</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">my_layout</span> <span class="o">=</span> <span class="no">Layout</span><span class="o">.</span><span class="n">new</span>
 <span class="n">my_layout</span><span class="o">[</span><span class="ss">:source</span><span class="p">,</span> <span class="ss">:main</span><span class="p">,</span> <span class="ss">:java</span><span class="o">]</span> <span class="o">=</span> <span class="s1">&#39;java&#39;</span>
 <span class="n">my_layout</span><span class="o">[</span><span class="ss">:source</span><span class="p">,</span> <span class="ss">:main</span><span class="p">,</span> <span class="ss">:resources</span><span class="o">]</span> <span class="o">=</span> <span class="s1">&#39;resources&#39;</span>
-</code></pre>
-</div>
-<p>Partial expansion also works, so you can specify the above layout using:</p>
+</code></pre></div><p>Partial expansion also works, so you can specify the above layout using:</p>
 <div class="highlight"><pre><code class="ruby"><span class="n">my_layout</span> <span class="o">=</span> <span class="no">Layout</span><span class="o">.</span><span class="n">new</span>
 <span class="n">my_layout</span><span class="o">[</span><span class="ss">:source</span><span class="p">,</span> <span class="ss">:main</span><span class="o">]</span> <span class="o">=</span> <span class="s1">&#39;&#39;</span>
-</code></pre>
-</div>
-<p>If you need anything more complex, you can always subclass <code>Layout</code> and add special handling in the <code>expand</code> method, you&#8217;ll find one such example in the <span class="caps">API</span> documentation.</p>
+</code></pre></div><p>If you need anything more complex, you can always subclass <code>Layout</code> and add special handling in the <code>expand</code> method, you&#8217;ll find one such example in the <span class="caps">API</span> documentation.</p>
 <p>The built-in tasks expand lists of symbols into relative paths, using the following convention:</p>
 <table>
 	<tr>
@@ -286,8 +268,7 @@
   <span class="c1"># This will work with different layouts.</span>
   <span class="n">package</span><span class="p">(</span><span class="ss">:jar</span><span class="p">)</span><span class="o">.</span><span class="n">include</span> <span class="n">path_to</span><span class="p">(</span><span class="ss">:source</span><span class="p">,</span> <span class="ss">:main</span><span class="p">,</span> <span class="ss">:etc</span><span class="p">,</span> <span class="s1">&#39;*&#39;</span><span class="p">)</span>
 <span class="k">end</span>
-</code></pre>
-</div>
+</code></pre></div>
       </div>
       <div id='footer'>Copyright &copy; 2007-2010 The Apache Software Foundation</div>
     </div>

Modified: buildr/site/index.html
URL: http://svn.apache.org/viewvc/buildr/site/index.html?rev=1529576&r1=1529575&r2=1529576&view=diff
==============================================================================
--- buildr/site/index.html (original)
+++ buildr/site/index.html Sun Oct  6 07:17:05 2013
@@ -118,15 +118,27 @@
 </ul>
 <p>So let&#8217;s get started.  You can <a href="quick_start.html">read the documentation online</a>, or <a href="buildr.pdf">download the <span class="caps">PDF</span></a>.</p>
 <h2 id="news">What&#8217;s New</h2>
-<p>Highlights from Buildr 1.4.12 (2013-05-04)</p>
+<p>Highlights from Buildr 1.4.13 (2013-10-02)</p>
 <ul>
-	<li>Added:  <span class="caps">BUILDR</span>-648 Add new package(:test_jar) packaging type. Submitted by Mike Pettypiece.</li>
-	<li>Fixed:  <span class="caps">BUILDR</span>-666 ZipFile.open modifies file regardless of usage. Reported by Pepijn Van Eeckhoudt, fix by Alex Boisvert.</li>
-	<li>Change: Moved to using TravisCI to test the Linux variants.</li>
-	<li>Added:  Make the location of the wsdl in generated source configurable in the wsgen addon.</li>
-	<li>Added:  Added support for SuperDevMode in gwt addon and upgraded to <span class="caps">GWT</span> 2.5.1 by default.</li>
-	<li>Change: <span class="caps">BUILDR</span>-664 Update Checkstyle addon so that extra_dependencies is empty by default. Submitted by Dieter Vrancken.</li>
-	<li>Fixed:  <span class="caps">BUILDR</span>-663 require &#8216;buildr&#8217; fails for Ruby 2.0.0.</li>
+	<li>Fixed:  Upgrade rjb dependency so that you can change JVMs by<br />
+          modifying JAVA_HOME rather than recompiling rjb.</li>
+	<li>Change: Update to TestNG 6.8.5.</li>
+	<li>Fixed:  Several Ruby 2.0.0 failures have been addressed.</li>
+	<li>Fixed:  Make archive-related operations use a deterministic ordering.</li>
+	<li>Added:  Initial support for simple integration of an asset pipeline.<br />
+          See &#8220;Compiling Assets&#8221; section in the manual.</li>
+	<li>Change: Improve the Intellij <span class="caps">IDEA</span> plugin substantially.</li>
+	<li>Change: Improve the gpg addon.</li>
+	<li>Fixed:  <span class="caps">BUILDR</span>-676 &#8211; Support the :dir option in Java::Command:java.<br />
+          Reported by John Roth.</li>
+	<li>Fixed:  Improve downloading from Maven Central to avoid caching and<br />
+          set the &#8220;User-Agent&#8221; http header.</li>
+	<li>Change: Change default scope of dependencies to &#8216;compile&#8217;. Submitted<br />
+          by Ingo Schmidt.</li>
+	<li>Fixed:  <span class="caps">BUILDR</span>-673 &#8211; Fix the option handling of the MultiTest test<br />
+          framework to behave as documented. Submitted by John Roth.</li>
+	<li>Added:  <span class="caps">BUILDR</span>-672 &#8211; Allow the user to modify the properties field in<br />
+          the checkstyle addon. Submitted by Wim C.</li>
 </ul>
 <p>This is a partial list &#8212; see the <a href="CHANGELOG"><span class="caps">CHANGELOG</span></a> for full details.</p>
 <h2 id="notices">Credits &amp; Notices</h2>

Modified: buildr/site/installing.html
URL: http://svn.apache.org/viewvc/buildr/site/installing.html?rev=1529576&r1=1529575&r2=1529576&view=diff
==============================================================================
--- buildr/site/installing.html (original)
+++ buildr/site/installing.html Sun Oct  6 07:17:05 2013
@@ -103,71 +103,47 @@
 <p>On <strong>RedHat/Fedora</strong> you can use yum to install Ruby and RubyGems, and then upgrade to the most recent version of RubyGems:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo yum install ruby rubygems ruby-devel gcc
 <span class="nv">$ </span>sudo gem update --system
-</code></pre>
-</div>
-<p>On <strong>Ubuntu</strong> you have to install several packages:</p>
+</code></pre></div><p>On <strong>Ubuntu</strong> you have to install several packages:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo apt-get install ruby-full ruby1.8-dev libopenssl-ruby build-essential
-</code></pre>
-</div>
-<p>If using Ubuntu 9.10 or earlier, the Debian package for <code>rubygems</code> will not allow you to install Buildr, so you need to install RubyGems from source:</p>
+</code></pre></div><p>If using Ubuntu 9.10 or earlier, the Debian package for <code>rubygems</code> will not allow you to install Buildr, so you need to install RubyGems from source:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>wget http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz
 <span class="nv">$ </span>tar xzf rubygems-1.3.1.tgz
 <span class="nv">$ </span><span class="nb">cd </span>rubygems-1.3.1
 <span class="nv">$ </span>sudo ruby setup.rb
 <span class="nv">$ </span>sudo ln -s /usr/bin/gem1.8 /usr/bin/gem
-</code></pre>
-</div>
-<p>Before installing Buildr, please set the <code>JAVA_HOME</code> environment variable to point to your <span class="caps">JDK</span> distribution.  Next, use Ruby Gem to install Buildr:</p>
+</code></pre></div><p>Before installing Buildr, please set the <code>JAVA_HOME</code> environment variable to point to your <span class="caps">JDK</span> distribution.  Next, use Ruby Gem to install Buildr:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem install buildr
-</code></pre>
-</div>
-<p>To upgrade to a new version or install a specific version:</p>
+</code></pre></div><p>To upgrade to a new version or install a specific version:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem update buildr
 <span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem install buildr -v 1.4.3
-</code></pre>
-</div>
-<h2 id="osx">Installing on OS X</h2>
+</code></pre></div><h2 id="osx">Installing on OS X</h2>
 <p><strong>The easy way:</strong> Use this script to <a href="scripts/install-osx.sh">install Buildr on OS X</a>.  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.</p>
 <p>You need to have the Apple Development Tools installed.  They are available on the Mac <span class="caps">OSX</span> installation CD.</p>
 <p class="note">Java Update 3 for Snow Leopard removes header files necessary to compile the native Ruby-Java Bridge (<span class="caps">RJB</span>) gem, so installing rjb gem may fail on OS X.  The solution is to install Java for Mac OS X 10.6 Update 3 Developer Package from http://connect.apple.com before <code>gem install</code>.</p>
 <p><strong>Using <span class="caps">RVM</span>?</strong> If you&#8217;re not using the built-in ruby on OS X (e.g., if you&#8217;re using <span class="caps">RVM</span>), you&#8217;ll need to force-install the platform-independent <span class="caps">RJB</span>:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>gem install rjb -v 1.3.3 --platform ruby
-</code></pre>
-</div>
-<p>The darwin pre-built binary seems to only work with the built-in ruby.</p>
+</code></pre></div><p>The darwin pre-built binary seems to only work with the built-in ruby.</p>
 <p><br></p>
 <p><strong>In details:</strong> 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.</p>
 <p>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 (<code>sudo port install ruby rb-rubygems</code>), Fink or the <a href="http://rubyosx.rubyforge.org/">Ruby One-Click Installer for OS X</a>.</p>
 <p>We recommend you first upgrade to the latest version of Ruby gems:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo gem update --system
-</code></pre>
-</div>
-<p>Before installing Buildr, please set the <code>JAVA_HOME</code> environment variable to point to your <span class="caps">JDK</span> distribution:</p>
+</code></pre></div><p>Before installing Buildr, please set the <code>JAVA_HOME</code> environment variable to point to your <span class="caps">JDK</span> distribution:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span><span class="nb">export </span><span class="nv">JAVA_HOME</span><span class="o">=</span>/Library/Java/Home
-</code></pre>
-</div>
-<p>To install Buildr:</p>
+</code></pre></div><p>To install Buildr:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem install buildr
-</code></pre>
-</div>
-<p>To upgrade to a new version or install a specific version:</p>
+</code></pre></div><p>To upgrade to a new version or install a specific version:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem update buildr
 <span class="nv">$ </span>sudo env <span class="nv">JAVA_HOME</span><span class="o">=</span><span class="nv">$JAVA_HOME</span> gem install buildr -v 1.3.4
-</code></pre>
-</div>
-<h2 id="windows">Installing on Windows</h2>
+</code></pre></div><h2 id="windows">Installing on Windows</h2>
 <p><strong>The easy way:</strong>  The easiest way to install Ruby is using the <a href="http://rubyinstaller.rubyforge.org/">one-click installer</a>.  Be sure to install Ruby 1.8.6; support for Ruby 1.9.x is still a work in progress.  Once installed, set the <code>JAVA_HOME</code> environment variable and run <code>gem install buildr --platform mswin32</code>.</p>
 <p><br></p>
 <p><strong>In details:</strong> Before installing Buildr, please set the <code>JAVA_HOME</code> environment variable to point to your <span class="caps">JDK</span> distribution.  Next, use Ruby Gem to install Buildr:</p>
 <div class="highlight"><pre><code class="sh">&gt; gem install buildr --platform mswin32
-</code></pre>
-</div>
-<p>To upgrade to a new version or install a specific version:</p>
+</code></pre></div><p>To upgrade to a new version or install a specific version:</p>
 <div class="highlight"><pre><code class="sh">&gt; gem update buildr
 &gt; gem install buildr -v 1.3.4 --platform mswin32
-</code></pre>
-</div>
-<h2 id="jruby">Installing for JRuby</h2>
+</code></pre></div><h2 id="jruby">Installing for JRuby</h2>
 <p><strong>The easy way:</strong> Use this bash script to <a href="scripts/install-jruby.sh">install Buildr on JRuby</a>.  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.6.1 in <code>/opt/jruby</code> and update the <code>PATH</code> variable in <code>~/.bash_profile</code> or <code>~/.profile</code>.</p>
 <p><br></p>
 <p><strong>In details:</strong> If you don&#8217;t already have JRuby 1.5.1 or later installed, you can download it from the <a href="http://www.jruby.org/download">JRuby site</a>.</p>
@@ -175,19 +151,13 @@
 <p>For Linux and OS X:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span><span class="nb">export </span><span class="nv">PATH</span><span class="o">=</span><span class="nv">$PATH</span>:<span class="o">[</span>path to JRuby<span class="o">]</span>/bin:<span class="nv">$JAVA_HOME</span>/bin
 <span class="nv">$ </span>jruby -S gem install buildr
-</code></pre>
-</div>
-<p>For Windows:</p>
+</code></pre></div><p>For Windows:</p>
 <div class="highlight"><pre><code class="sh">&gt; <span class="nb">set </span><span class="nv">PATH</span><span class="o">=</span>%PATH%;<span class="o">[</span>path to JRuby<span class="o">]</span>/bin;%JAVA_HOME%/bin
 &gt; jruby -S gem install buildr
-</code></pre>
-</div>
-<p>To upgrade to a new version or install a specific version:</p>
+</code></pre></div><p>To upgrade to a new version or install a specific version:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>jruby -S gem update buildr
 <span class="nv">$ </span>jruby -S gem install buildr -v 1.3.4
-</code></pre>
-</div>
-<p><strong>Important: Running JRuby and Ruby side by side</strong></p>
+</code></pre></div><p><strong>Important: Running JRuby and Ruby side by side</strong></p>
 <p>Ruby and JRuby maintain separate Gem repositories, and in fact install slightly different versions of the Buildr Gem (same functionality, different dependencies).  Installing Buildr for Ruby does not install it for JRuby and vice versa.</p>
 <p>If you have JRuby installed but not Ruby, the <code>gem</code> and <code>buildr</code> commands will use JRuby.  If you have both JRuby and Ruby installed, follow the instructions below.  To find out if you have Ruby installed (some operating systems include it by default), run <code>ruby --version</code> from the command line.</p>
 <p>To work exclusively with JRuby, make sure it shows first on the path, for example, by setting <code>PATH=/opt/jruby/bin:$PATH</code>.</p>
@@ -198,25 +168,19 @@
 <span class="nv">$ </span><span class="c"># with JRuby</span>
 <span class="nv">$ </span>jruby -S gem install buildr
 <span class="nv">$ </span>jruby -S buildr
-</code></pre>
-</div>
-<p>Run <code>buildr --version</code> from the command line to find which version of Buildr you are using by default.  If you see <code>(JRuby ...)</code>, Buildr is running on that version of JRuby.</p>
+</code></pre></div><p>Run <code>buildr --version</code> from the command line to find which version of Buildr you are using by default.  If you see <code>(JRuby ...)</code>, Buildr is running on that version of JRuby.</p>
 <h2>Using multiple versions of Buildr</h2>
 <p>Rubygems makes it possible to install several versions of Buildr side-by-side on the same system.  If you want to run a specific version, you can do so by adding the version number between underscores (&#8216;_&#8217;) as the first command-line parameter.  For example,</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>buildr _1.3.4_ clean   <span class="c"># runs Buildr v1.3.4</span>
 
 <span class="nv">$ </span>buildr _1.4.4_ clean   <span class="c"># runs Buildr v1.4.4</span>
-</code></pre>
-</div>
-<p class="note">There are two `buildr` executables installed by Rubygems.  One script serves to select the specified (or default) version of Buildr and is typically found under `/usr/bin/buildr` or `/var/lib/gems/1.8/bin/buildr`. The exact location will vary depending on your system.   The other script is the Buildr bootstrap per se and can be found under the specific version of Buildr, e.g, `/var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr`.   The first script should be on your `<span class="caps">PATH</span>`.   The second script should not be called directly and should not be on your `<span class="caps">PATH</span>`.</p>
+</code></pre></div><p class="note">There are two `buildr` executables installed by Rubygems.  One script serves to select the specified (or default) version of Buildr and is typically found under `/usr/bin/buildr` or `/var/lib/gems/1.8/bin/buildr`. The exact location will vary depending on your system.   The other script is the Buildr bootstrap per se and can be found under the specific version of Buildr, e.g, `/var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr`.   The first script should be on your `<span class="caps">PATH</span>`.   The second script should not be called directly and should not be on your `<span class="caps">PATH</span>`.</p>
 <h2 id="running">Running Buildr</h2>
 <p>You need a <strong>Buildfile</strong>, a build script that tells Buildr all about the projects it&#8217;s building, what they contain, what to produce, and so on.  The Buildfile resides in the root directory of your project.  We&#8217;ll talk more about it in <a href="projects.html">the next chapter</a>.  If you don&#8217;t already have one, ask Buildr to create it by running <code>buildr</code>.</p>
 <p class="tip">You&#8217;ll notice that Buildr creates a file called <code>buildfile</code>.  It&#8217;s case sensitive, but Buildr will look for either <code>buildfile</code> or <code>Buildfile</code>.</p>
 <p>You use Buildr by running the <code>buildr</code> command:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>buildr <span class="o">[</span>options<span class="o">]</span> <span class="o">[</span>tasks<span class="o">]</span> <span class="o">[</span><span class="nv">name</span><span class="o">=</span>value<span class="o">]</span>
-</code></pre>
-</div>
-<p>There are several options you can use, for a full list of options type <code>buildr --help</code>:</p>
+</code></pre></div><p>There are several options you can use, for a full list of options type <code>buildr --help</code>:</p>
 <table>
 	<tr>
 		<th>Option                  </th>
@@ -268,30 +232,22 @@
 buildr clean build
 <span class="c"># Package and install</span>
 buildr install
-</code></pre>
-</div>
-<p>If you don&#8217;t specify a task, Buildr will run the <a href="building.html"><code>build</code> task</a>, compiling source code and running test cases.  Running a task may run other tasks as well, for example, running the <code>install</code> task will also run <code>package</code>.</p>
+</code></pre></div><p>If you don&#8217;t specify a task, Buildr will run the <a href="building.html"><code>build</code> task</a>, compiling source code and running test cases.  Running a task may run other tasks as well, for example, running the <code>install</code> task will also run <code>package</code>.</p>
 <p>There are several <a href="settings_profiles.html#env_vars">environment variables</a> that let you control how Buildr works, for example, to skip test cases during a build, or specify options for the <span class="caps">JVM</span>.  Depending on the variable, you may want to set it once in your environment, or set a different value each time you run Buildr.</p>
 <p>For example:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span><span class="nb">export </span><span class="nv">JAVA_OPTS</span><span class="o">=</span><span class="s1">&#39;-Xms1g -Xmx1g&#39;</span>
 <span class="nv">$ </span>buildr <span class="nv">TEST</span><span class="o">=</span>no
-</code></pre>
-</div>
-<h2 id="help">Help Tasks</h2>
+</code></pre></div><h2 id="help">Help Tasks</h2>
 <p>Buildr includes a number of informative tasks.  Currently that number stands at two, but we&#8217;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 <code>buildr --help</code>.</p>
 <p>To start with, type:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>buildr <span class="nb">help</span>
-</code></pre>
-</div>
-<p>You can list the name and description of all your projects using the <code>help:projects</code> task.  For example:</p>
+</code></pre></div><p>You can list the name and description of all your projects using the <code>help:projects</code> task.  For example:</p>
 <div class="highlight"><pre><code class="sh"><span class="nv">$ </span>buildr <span class="nb">help</span>:projects
 killer-app                 <span class="c"># Code. Build. ??? Profit!</span>
 killer-app:teh-api         <span class="c"># Abstract classes and interfaces</span>
 killer-app:teh-impl        <span class="c"># All those implementation details</span>
 killer-app:la-web          <span class="c"># What our users see</span>
-</code></pre>
-</div>
-<p>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 <code>desc</code> method before the project or task definition.</p>
+</code></pre></div><p>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 <code>desc</code> method before the project or task definition.</p>
 <p>So next let&#8217;s talk about <a href="projects.html">projects</a>.</p>
 <h2 id="more">Learning More</h2>
 <p><strong>Ruby</strong>  It pays to pick up Ruby as a second (or first) programming language. It&#8217;s fun, powerful and slightly addictive.  If you&#8217;re interested in learning Ruby the language, a good place to start is <a href="http://www.pragprog.com/titles/ruby/programming-ruby">Programming Ruby: The Pragmatic Programmer&#8217;s Guide</a>, fondly known as the <em>Pickaxe book</em>.</p>