assaf-buildr 1.3.3

data/doc/pages/testing.textile

@@ -0,0 +1,212 @@
+h1. Testing
+
+Untested code is broken code, so we take testing seriously.  Off the bat you get to use either JUnit or TestNG for writing unit tests and integration tests. And you can also add your own framework, or even script tests using Ruby.  But= first, let's start with the basics.
+
+
+h2. Writing Tests
+
+Each project has a @TestTask@ that you can access using the @test@ method. @TestTask@ reflects on the fact that each project has one task responsible for getting the tests to run and acting on the results.  But in fact there are several tasks that do all the work, and a @test@ task coordinates all of that.
+
+The first two tasks to execute are @test.compile@ and @test.resources@.  They work similar to @compile@ and @resources@, but uses a different set of directories.  For example, Java tests compile from the @src/test/java@ directory into the @target/test/classes@ directory, while resources are copied from @src/test/resources@ into @target/test/resources@.
+
+The @test.compile@ task will run the @compile@ task first, then use the same dependencies to compile the test classes.  That much you already assumed.  It also adds the test framework (e.g. JUnit, TestNG) and JMock to the dependency list.  Less work for you.
+
+If you need more dependencies, the best way to add them is by calling @test.with@.  This method adds dependencies to both @compile.dependencies@ (for compiling) and @test.dependencies@ (for running).  You can manage these two dependency lists separately, but using @test.with@ is good enough in more cases.
+
+Once compiled, the @test@ task runs all the tests.
+
+Different languages use different test frameworks.  You can find out more about available test frameworks in the "Languages":languages.html section.
+
+
+h2. Excluding Tests and Ignoring Failures
+
+If you have a lot of tests that are failing or just hanging there collecting dusts, you can tell Buildr to ignore them.  You can either tell Buildr to only run specific tests, for example:
+
+{{{!ruby
+test.include 'com.acme.tests.passing.*'
+}}}
+
+Or tell it to exclude specific tests, for example:
+
+{{{!ruby
+test.exclude '*FailingTest', '*FailingWorseTest'
+}}}
+
+Note that we're always using the package qualified class name, and you can use star (@*@) to substitute for any set of characters.
+
+When tests fail, Buildr fails the @test@ task.  This is usually a good thing, but you can also tell Buildr to ignore failures by resetting the @:fail_on_failure@ option:
+
+{{{!ruby
+test.using :fail_on_failure=>false
+}}}
+
+Besides giving you a free pass to ignore failures, you can use it for other causes, for example, to be somewhat forgiving:
+
+{{{!ruby
+test do
+  fail 'More than 3 tests failed!' if test.failed_tests.size > 3
+end
+}}}
+
+The @failed_tests@ collection holds the names of all classes with failed tests. And there's @classes@, which holds the names of all test classes.  Ruby arithmetic allows you to get the name of all passed test classes with a simple @test.classes – test.failed_tests@.  We'll let you imagine creative use for these two.
+
+
+h2. Running Tests
+
+It's a good idea to run tests every time you change the source code, so we wired the @build@ task to run the @test@ task at the end of the build.  And conveniently enough, the @build@ task is the default task, so another way to build changes in your code and run your tests:
+
+{{{!sh
+$ buildr
+}}}
+
+That only works with the local @build@ task and any local task that depends on it, like @package@, @install@ and @upload@.  Each project also has its own @build@ task that does not invoke the @test@ task, so @buildr build@ will run the tests cases, but @buildr foo:build@ will not.
+
+While it's a good idea to always run your tests, it's not always possible. There are two ways you can get @build@ to not run the @test@ task.  You can set the environment variable @test@ to @no@ (but @skip@ and @off@ will also work). You can do that when running Buildr:
+
+{{{!sh
+$ buildr test=no
+}}}
+
+Or set it once in your environment:
+
+{{{!sh
+$ export TEST=no
+$ buildr
+}}}
+
+If you're feeling really adventurous, you can also disable tests from your Buildfile or @buildr.rb@ file, by setting @options.test = false@. We didn't say it's a good idea, we're just giving you the option.
+
+The @test@ task is just smart enough to run all the tests it finds, but will accept include/exclude patterns.  Often enough you're only working on one broken test and you only want to run that one test.  Better than changing your Buildfile, you can run the @test@ task with a pattern.  For example:
+
+{{{!sh
+$ buildr test:KillerAppTest
+}}}
+
+Buildr will then run only tests that match the pattern @KillerAppTest@.  It uses pattern matching, so @test:Foo@ will run @com.acme.FooTest@ and @com.acme.FooBarTest@.  With Java, you can use this to pick a class name, or a package name to run all tests in that package, or any such combination.  In fact, you can specify several patterns separated with commas.  For example:
+
+{{{!sh
+$ buildr test:FooTest,BarTest
+}}}
+
+As you probably noticed, Buildr will stop your build at the first test that fails.  We think it's a good idea, except when it's not.  If you're using a continuous build system, you'll want a report of all the failed tests without stopping at the first failure.  To make that happen, set the environment variable @test@ to "all", or the Buildr @options.test@ option to @:all@.  For example:
+
+{{{!sh
+$ buildr package test=all
+}}}
+
+We're using @package@ and not @build@ above.  When using a continuous build system, you want to make sure that packages are created, contain the right files, and also run the integration tests.
+
+
+h2. Integration Tests
+
+So far we talked about unit tests.  Unit tests are run in isolation on the specific project they test, in an isolated environment, generally with minimal setup and teardown.  You get a sense of that when we told you tests run after the @build@ task, and include JMock in the dependency list.
+
+In contrast, integration tests are run with a number of components, in an environment that resembles production, often with more complicates setup and teardown procedures.  In this section we'll talk about the differences between running unit and integration tests.
+
+You write integration tests much the same way as you write unit tests, using @test.compile@ and @test.resources@.  However, you need to tell Buildr that your tests will execute during integration test.  To do so, add the following line in your project definition:
+
+{{{!ruby
+test.using :integration
+}}}
+
+Typically you'll use unit tests in projects that create internal modules, such as JARs, and integration tests in projects that create components, such as WARs and EARs.  You only need to use the @:integration@ option with the later.
+
+To run integration tests on the current project:
+
+{{{!sh
+$ buildr integration
+}}}
+
+You can also run specific tests cases, for example:
+
+{{{!sh
+$ buildr integration:ClientTest
+}}}
+
+If you run the @package@ task (or any task that depends on it, like @install@ and @upload@), Buildr will first run the @build@ task and all its unit tests, and then create the packages and run the integration tests.  That gives you full coverage for your tests and ready to release packages.  As with unit tests, you can set the environment variable @test@ to "no" to skip integration tests, or "all" to ignore failures.
+
+
+h2. Using Setup and Teardown
+
+Some tests need you to setup an environment before they run, and tear it down afterwards.  The test frameworks (JUnit, TestNG) allow you to do that for each test.  Buildr provides two additional mechanisms for dealing with more complicated setup and teardown procedures.
+
+Integration tests run a setup task before the tests, and a teardown task afterwards.  You can use this task to setup a Web server for testing your Web components, or a database server for testing persistence.  You can access either task by calling @integration.setup@ and @integration.teardown@.  For example:
+
+{{{!ruby
+integration.setup { server.start ; server.deploy }
+integration.teardown { server.stop }
+}}}
+
+Depending on your build, you may want to enhance the setup/teardown tasks from within a project, for example, to populate the database with data used by that project's test, or from outside the project definition, for example, to start and stop the Web server.
+
+Likewise, each project has its own setup and teardown tasks that are run before and after tests for that specific project.  You can access these tasks using @test.setup@ and @test.teardown@.
+
+
+h2. Testing Your Build
+
+So you got the build running and all the tests pass, binaries are shipping when you find out some glaring omissions.  The license file is empty, the localized messages for Japanese are missing, the CSS files are not where you expect them to be.  The fact is, some errors slip by unit and integration tests.  So how do we make sure the same mistake doesn't happen again?
+
+Each project has a @check@ task that runs just after packaging.  You can use this task to verify that your build created the files you wanted it to create. And to make it extremely convenient, we introduced the notion of expectations.
+
+You use the @check@ method to express and expectation.  Buildr will then run all these expectations against your project, and fail at the first expectation that doesn't match.  An expectation says three things.  Let's look at a few examples:
+
+{{{!ruby
+check package(:war), 'should exist' do
+  it.should exist
+end
+check package(:war), 'should contain a manifest' do
+  it.should contain('META-INF/MANIFEST.MF')
+end
+check package(:war).path('WEB-INF'), 'should contain files' do
+  it.should_not be_empty
+end
+check package(:war).path('WEB-INF/classes'), 'should contain classes' do 
+  it.should contain('**/*.class')
+end
+check package(:war).entry('META-INF/MANIFEST'), 'should have license' do
+  it.should contain(/Copyright (C) 2007/)
+end
+check file('target/classes'), 'should contain class files' do
+  it.should contain('**/*.class')
+end
+check file('target/classes/killerapp/Code.class'), 'should exist' do
+  it.should exist
+end
+}}}
+
+The first argument is the subject, or the project if you skip the first argument.  The second argument is the description, optional, but we recommend using it.  The method @it@ returns the subject.
+
+You can also write the first expectation like this:
+
+{{{!ruby
+check do
+  package(:jar).should exist
+end
+}}}
+
+We recommend using the subject and description, they make your build easier to read and maintain, and produce better error messages.
+
+There are two methods you can call on just about any object, called @should@ and @should_not@.  Each method takes an argument, a matcher, and executes that matcher.  If the matcher returns false, @should@ fails.  You can figure out what @should_not@ does in the same case.
+
+Buildr provides the following matchers:
+
+|_. Method |_. Checks that ... |
+| @exist@   | Given a file task checks that the file (or directory) exists. |
+| @empty@   | Given a file task checks that the file (or directory) is empty. |
+| @contain@ | Given a file task referencing a file, checks its contents, using string or regular expression.  For a file task referencing a directory, checks that it contains the specified files; global patterns using @*@ and @**@ are allowed. |
+
+All these matchers operate against a file task.  If you run them against a ZipTask (including JAR, WAR, etc) they can also check the contents of the ZIP file.  And as you can see in the examples above, you can also run them against a path in a ZIP file, checking its contents as if it was a directory, or against an entry in a ZIP file, checking the content of that file.
+
+p(note). The @package@ method returns a package task based on packaging type, identifier, group, version and classifier.  The last four are inferred, but if you create a package with different specifications (for example, you specify a classifier) your checks must call @package@ with the same qualifying arguments to return the very same package task.
+
+Buildr expectations are based on RSpec.  "RSpec":http://rspec.info/ is the behavior-driven development framework we use to test Buildr itself.  Check the RSpec documentation if want to see all the supported matchers, or want to write your own.
+
+
+h2. Behaviour-Driven Development
+
+Buildr supports several Behaviour-Driven Development(BDD) frameworks for testing your projects.  Buildr follows each framework naming conventions, searching for files under the @src/spec/{lang}@ directory.
+
+You can learn more about each BDD framework in the "Languages":languages.html section.
+
+
+Next, let's talk about "customizing your environment and using profiles":settings_profiles.html

data/doc/pages/troubleshooting.textile

@@ -0,0 +1,103 @@
+h1. Troubleshooting
+
+Common troubleshooting tips collected from the mailing list.
+
+
+h2.  Running out of heap space
+
+You can give the JVM more heap space by setting the @JAVA_OPTS@ environment variables.  This environment variable provides arguments for staring the JVM. For example, to set the heap space to 1GB:
+
+{{{!sh
+$ export "JAVA_OPTS=-Xms1g -Xmx1g"
+$ buildr compile
+}}}
+
+If you're sharing the build with other developers, you'll want to specify these options in the Buildfile itself.  You can set the environment variable within the Buildfile, but make sure to do so at the very top of the Buildfile.
+
+For example:
+
+{{{!ruby
+ENV['JAVA_OPTS'] = '-Xms1g -Xmx1g'
+}}}
+
+
+h2.  RJB fails to compile
+
+On Linux, BSD and Cygwin, RJB locates the JDK headers files -- which it uses to compile a native C extension -- based on the @JAVA_HOME@ environment variable. Make sure @JAVA_HOME@ points to the JDK, not JRE.
+
+If you are using @sudo gem install@, note that some environments do not pass the @JAVA_HOME@ environment variable over to @sudo@.  To get around this, run @gem@ with the @env JAVA_HOME=$JAVA_HOME@ option:
+
+{{{!sh
+$ sudo env JAVA_HOME=$JAVA_HOME gem install buildr
+}}}
+
+
+h2.  Segmentation Fault when running Java code
+
+This is most likely a JVM inconsistency, for example, when part of the RJB library uses JDK 1.6, the other part uses JDK 1.5.
+
+During installation RJB builds a native C extension using header files supplied by the JVM, and compiles a Java bridge class using the Javac.  It is possible for RJB to use two different versions of the JVM, for example, if @JAVA_HOME@ points to JDK 1.5, but @/usr/bin/javac@ points to JDK 1.6.
+
+Make sure @JAVA_HOME@ and @/usr/bin/javac@ both point to the same JDK:
+
+{{{!sh
+echo $JAVA_HOME
+ls -l /usr/bin/javac
+}}}
+
+*Note:*  It seems that RJB works with Java 6, except when it doesn't, and for a few people it doesn't.  In that case, either switch to Java 1.5, or simply run Buildr on JRuby using Java 6.
+
+
+h2.  Bugs resulting from a dangling comma or period
+
+Ruby statements don't need a delimiter and can span multiple lines, which can lead to bugs resulting from dangling commas and periods left at the end of the line.  For example:
+
+{{{!ruby
+compile.with 'org.apache.axis2:axis2:jar:1.2',
+test.with 'log4j:log4j:jar:1.1'
+}}}
+
+This is actually a single method call with two arguments, separated by a comma. The second argument is the result of calling @test.with@, and makes the test task a pre-requisite of the compile task, leading to a circular dependency.
+
+As you can imagine this happens usually after editing, specifically for commas and periods which are small enough that you won't notice them from a cursory glance at the code, so if all else fails, search for lines that end with one of these characters.
+
+
+h2.  Missing POM breaks transitive dependencies
+
+Occasionally, artifacts are deployed to remote repositories with missing or broken POMs.  Buildr will fail when attempting to resolve transitive dependencies with broken or missing POMs.
+
+In this particular case, failing is doing the right thing.  There's no way for Buildr to tell whether the POM is nowhere to be found, or just a temporary problem accessing the remote server.
+
+If you can determine that the POM file is missing you can work around the problem in three ways.  If you published the artifact, make the release again, getting it to upload the missing files.
+
+If the source repository is not under your control, but you are also using your own repository for the project, you can always create a dummy POM in your own repository.  Buildr will attempt to download the file from either repository, using the first file it finds.
+
+Alternatively, you can make Buildr create a dummy POM file in the local repository, instead of downloading it from a remote repository.  This example creates a dummy POM for Axis JAX-RPC:
+
+{{{!ruby
+artifact 'axis:axis-jaxrpc:pom:1.3' do |task|
+  write task.name, <<-POM
+    <project>
+      <modelVersion>4.0.0</modelVersion>
+      <groupId>axis</groupId>
+      <artifactId>axis-jaxrpc</artifactId>
+      <version>1.4</version>
+    </project>
+  POM
+end
+}}}
+
+
+h2. Buildr fails to run after install with a "stack level too deep (SystemStackError)" error
+
+A particular quirk of an existing Ruby setup can cause problems when running Buildr.  If a system already has several Ruby directories that are in the @PATH@, it is often nice (appropriate?) to have them in @RUBYLIB@ as well (to be able to require them).  If there are several of them a user may decide that @RUBYLIB=$PATH@ is a good way to handle this (or some less automated method that has the same effect).
+
+The culprit is having the Gem's binary directory show up in @RUBYLIB@.  For example, Buildr's @bin/buildr@ includes this line:
+
+{{{!sh
+require 'buildr'
+}}}
+
+Under normal circumstances, this tells RubyGems to load @buildr.rb@ from the Gem's library directory.  When @RUBYLIB@ points to the Gem's @bin@ directory, it ends up loading itself repeatedly. 
+
+To solve this, remove Buildr's @bin@ directory from @RUBYLIB@.  Removing all directories that you don't actually need is better (other Gems may have the same problem).

data/doc/pages/whats_new.textile

@@ -0,0 +1,323 @@
+h1.  What's New
+
+h2.  Buildr 1.3.3
+
+* Support for "JtestR":http://jtestr.codehaus.org/ test framework.
+* Support for "Emma":http://emma.sourceforge.net/ code coverage tool.
+* Growl notifications (OS X only).
+* Starting with this release you can use the @build.yml@ file to control versions of various 3rd party libraries, e.g. Ant, JUnit, ScalaCheck.
+* The _release_ task now supports alternative SVN repository layouts. Releases are tagged in SVN using the version number, but you can customize the tag name (see @Releases.tag_name@). The @NEXT_VERSION@ constant is no longer used during the release process.
+* This release is tested against JRuby 1.1.3 and JRuby 1.1.4. There are also some improvements towards Ruby 1.9 support.
+* 27 other bug fixes and minor changes, see the "CHANGELOG":changelog.html for full details.
+
+
+h2.  Buildr 1.3.2
+
+* New @--prereqs@ command line argument lists all the tasks and their dependencies. You can also filter specific tasks by following with a regular expression, for example, @--prereqs foo@.
+* Upgraded to latest release of Net::SSH, Net::SFTP, RubyForge and RubyGems.
+* Upgraded to JUnit 4.4 and fixed case where abstract classes extending TestCase would lead to tests failing.
+* The target/test/class and /resources directories now come first in the classpath, ahead of any code compiled code and resources copied over from src/main.
+* Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
+* Fixed: BUILDR-91 When doing a release, buildr should spawn the same version of buildr
+* Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
+* Fixed: BUILDR-95: Only download Scala test framework artifacts when required
+* Fixed: BUILDR-100 Directory structure documentation needs updating.
+* Fixed: Installation instructions updated for RubyGems 1.2.0.
+
+
+h2.  Buildr 1.3.1
+
+* Fixed to specific Gem dependencies, so should install cleanly on Windows.
+* Buildr now supports publishing files to HTTP server for remote repositories that support HTTP uploads (PUT).
+* Buildr now supports reading files from SFTP server and upgrades to  Net::SSH 2.0 and Net::SFTP 2.0.
+* HTTP downloads now accept URLs with query parameters (Tommy Knowlton).
+* On OS X if you are not using the default JDK, you can set the JAVA_HOME environment variable to point to any other JDK (Nathan Hamblen).
+* JUnit properly passes options[:environment] as environment variables to the test case.  In addition options[:java_args] are now passed as arguments to the JVM, for example to set heap size, only applicable when forking (the default mode when running JUnit).
+* Fixed BUILDR-75: Filter now runs if there's a target directory, even if there are no source files to copy over, and creates an empty target directory.  The previous behavior caused some problems with code that checked if resource.target was nil, but didn't check if there are any resource.sources to process.
+* Added the jibx_bind method to use JiBX for Java<=>XML binding (by David Peterson).
+
+
+h2.  Buildr 1.3
+
+h3.  Multiple Languages
+
+The main focus of this release is supporting multiple languages for compiling and testing.
+
+For each project, Buildr will attempt to infer which compiler to use based on the source files it finds, for example, if it finds @.java@ files in the @src/main/java@ directory, it will switch to the javac compiler, if it finds @.scala@ files in the @src/main/scala@ directory, to the scalac compiler and so forth.
+
+Different compilers may use different target directory, @target/classes@ is picked for JVM compilers (Java, Scala, Groovy, etc), so resources are not copied to their own directory, @target/resources@.  The prepare task has been removed.
+
+Not all languages have classpaths, so @compile.classpath@ is now known as @compile.dependencies@, but the old attribute still exists for backward compatibility.
+
+Also, for consistency, the test target directories have changed to @target/test/classes@ and @target/test/resources@, respectively.
+
+Speaking of tests, you can compile code in one language and use a different language to test it, say, if you're interested in compiling Java code and testing it with Ruby, or compiling Flash and running a Java test suite.
+
+As before, you can pick the test framework by calling @test.using(<framework>)@.  Buildr will attempt to pick one by default, for example, if the tests are written in Java, it will default to JUnit.
+
+And, since not all languages package to JARs, the default packaging is either inferred from the compiler (so @:jar@ when compiling Java code), otherwise to @:zip@.  All this defaulting means that @package()@ with no arguments does the right thing in more cases, and most probably won't break anyone's buildfiles.
+
+I've tried to keep the compiler API as simple as possible, making it easy to add new compilers; however, I had to change the test framework API to accommodate the new features, so old test frameworks will not work on 1.3.
+
+
+h3.  Scala Support
+
+Buildr now supports "Scala":http://www.scala-lang.org/, using both native and  fast Scala compiler.
+
+Read more about "using Scala":languages.html#scala.
+
+
+h3.  Groovy Support
+
+Buildr now supports Groovy, using the Groovyc Ant task.
+
+Read more about "using Groovy":languages.html#groovy.
+
+
+h3.  Packaging Files
+
+The @package@ method is convenient enough that you can now use it to generate artifacts, an in addition to generate regular file tasks, specifying the file name using the @:file@ attribute.  For example:
+
+{{{!ruby
+package :zip, :file=>_('target/interesting.zip')
+}}}
+
+Since this package is not an artifact and does not have a specification, it will not automatically install itself in the local repository or upload to a remote repository.  For these, use the @package@ method as before.
+
+Read more about "the package method":packaging.html#specifying_and_referencing_packages.
+
+
+h3.  Packaging EARs
+
+EAR packages support four component types:
+
+|_. Argument  |_. Component                     |
+| @:war@      | J2EE Web Application (WAR).     |
+| @:ejb@      | Enterprise Java Bean (JAR).     |
+| @:jar@      | J2EE Application Client (JAR).  |
+| @:lib@      | Shared library (JAR).           |
+
+This example shows two ways for adding components built by other projects:
+
+{{{!ruby
+package(:ear) << project('coolWebService').package(:war)
+package(:ear).add project('commonLib') # By default, the JAR package
+}}}
+
+EAR packages include an @application.xml@ file in the @META-INF@ directory that describes the application and its component.  This file is created for you during packaging, by referencing all the components added to the EAR.  There are a couple of things you will typically want to change.
+
+* *display-name* -- The application's display name defaults to the project's identifier.  You can change that by setting the @display_name@ attribute.
+
+* *context-root* -- WAR components specify a context root, based on the package identifier, for example, "cool-web-1.0.war" will have the context root "cool-web".  To specify a different context root, add the WAR package with the @context_root@ option.
+
+"Read more ...":packaging.html#packaging_ears
+
+
+h3.  JRuby Support
+
+We now offer two versions of Buildr, one for Ruby and one for JRuby.  They're exactly the same, except the Ruby version will also install RJB (Ruby Java Bridge), the JRuby version obviously can do well without it.
+
+"Read more ...":download.html#jruby
+
+Buildr provides a "Nailgun":http://www.martiansoftware.com/nailgun/index.html server when running on JRuby. Using the integrated BuildrServer allows for  faster task execution and avoid frequent JVM startup overhead. 
+
+"Read more ...":more_stuff.html#nailgun
+
+
+h3. Behaviour-Driven Development
+
+Given that many languages are now supported by Buildr, the same is true for testing, the convention is to store BDD files under the @src/spec/{lang}@  directory.  The following table shows the framework's name you can use to select them  for your projects. Buildr follows each framework's naming convention.
+
+|_. test.using     |_. Test file name convention                  |
+| @:jbehave@       |  @src/spec/java/**/*Behaviour.java@            |
+| @:rspec@         |  @src/spec/ruby/**/*_spec.rb@                  |
+| @:easyb@         |  @src/spec/groovy/**/*{Story,Behavior}.groovy@ |
+
+"Read more ...":testing.html#bdd
+
+
+h3.  Profiles
+
+Different environments may require different configurations, some you will want to control with code, others you will want to specify in the profiles file.
+
+The profiles file is a YAML file called @profiles.yaml@ that you place in the same directory as the Buildfile.  We selected YAML because it's easier to read and edit than XML.
+
+For example, to support three different database configurations, we could write:
+
+{{{!yaml
+# HSQL, don't bother storing to disk.
+development:
+  db: hsql
+  jdbc: hsqldb:mem:devdb
+
+# Make sure we're not messing with bigstrong.
+test:
+  db: oracle
+  jdbc: oracle:thin:@localhost:1521:test
+
+# The real deal.
+production:
+  db: oracle
+  jdbc: oracle:thin:@bigstrong:1521:mighty
+}}}
+
+You can also use profiles to specify default filters for the "@resources@ task":building.html#resources.
+
+"Read more ...":settings_profiles.html#profiles
+
+
+h3.  Settings and build YAML files
+
+In addition to profiles, we also allow you to specify personal and build settings using two YAML files.
+
+Personal settings are placed in the @.buildr/settings.yaml@ file under your home directory. Settings stored there will be applied the same across all builds.
+
+For example:
+
+{{{!yaml
+# The repositories hash is read automatically by buildr.
+repositories:
+
+  # customize user local maven2 repository location
+  local: some/path/to/my_repo
+
+  relase_to:
+    url: http://intra.net/maven2
+    username: john
+    password: secret
+
+# You can place settings of your own, and reference them 
+# on buildfiles. 
+im:
+  server: jabber.company.com
+  usr: notifier@company-jabber.com
+  pwd: secret
+}}}
+
+"Read more ...":settings_profiles.html#personal_settings
+
+Build settings are placed in the @build.yaml@ file located in the same directory that the @buildfile@. Normally this file would be managed by the project revision control system, so settings here are shared between developers.
+
+For example:
+
+{{{!yaml
+# This project requires the following ruby gems, buildr addons
+gems: 
+  # Suppose we want to notify developers when testcases fail.
+  - buildr-twitter-notifier-addon >=1
+  # we test with ruby mock objects
+  - mocha
+  - ci_reporter
+
+# The artifact declarations will be automatically loaded by buildr, so that
+# you can reference artifacts by name (a ruby-symbol) on your buildfile.
+artifacts:
+  spring: org.springframework:spring:jar:2.0
+  log4j: log4j:log4j:jar:1.0
+  j2ee: geronimo-spec:geronimo-spec:j2ee:jar:1.4-rc4
+
+# Of course project settings can be defined here
+jira: 
+  uri: https://jira.corp.org
+}}}
+
+"Read more ...":settings_profiles.html#build_settings
+
+
+h3.  Using Gems for extensions and 3rd party libraries
+
+"RubyGems":http://rubygems.rubyforge.org provides the @gem@ command line tool that you can use to search, install, upgrade, package and distribute gems. It installs all gems into a local repository that is shared across your builds and all other Ruby applications you may have running.  You can install a gem from a local file, or download and install it from any number of remote repositories.
+
+If your build depends on other gems, you will want to specify these dependencies as part of your build and check that configuration into source control.  That way you can have a specific environment that will guarantee repeatable builds, whether you're building a particular version, moving between branches, or joining an existing project.  Buildr will take care of installing all the necessary dependencies, which you can then manage with the @gem@ command.
+
+Use the @build.yaml@ file to specify these dependencies (see "Build Settings":settings_profiles.html#build_settings for more information), for example:
+
+{{{!yaml
+# This project requires the following gems
+gems: 
+  # Suppose we want to notify developers when testcases fail.
+  - buildr-twitter-notifier-addon >=1
+  # we test with ruby mock objects
+  - mocha
+  - ci_reporter
+}}}
+
+"Read more ...":more_stuff.html#using_gems
+
+
+h3.  New API for accessing Java libraries
+
+Java classes are accessed as static methods on the @Java@ module, for example:
+
+{{{!ruby
+str = Java.java.lang.String.new('hai!')
+str.toUpperCase
+=> 'HAI!'
+Java.java.lang.String.isInstance(str)
+=> true
+Java.com.sun.tools.javac.Main.compile(args)
+}}}
+
+The @classpath@ attribute allows Buildr to add JARs and directories to the classpath, for example, we use it to load Ant and various Ant tasks, code generators, test frameworks, and so forth.
+
+For example, Ant is loaded as follows:
+
+{{{!ruby
+Java.classpath << 'org.apache.ant:ant:jar:1.7.0'
+}}}
+
+Artifacts can only be downloaded after the Buildfile has loaded, giving it a chance to specify which remote repositories to use, so adding to classpath does not by itself load any libraries.  You must call @Java.load@ before accessing any Java classes to give Buildr a chance to load the libraries specified in the classpath.
+
+"Read more ...":more_stuff.html#using_java_libraries
+
+
+h3.  Creating Extensions
+
+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
+class Project
+  include MyExtension
+end
+}}}
+
+You can also extend a given project instance and only that instance by extending it with the module:
+
+{{{!ruby
+define 'foo' do
+  extend MyExtension
+end
+}}}
+
+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.
+
+"Read more ...":extending.html#creating_extensions
+
+
+h3.  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.
+
+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.
+
+"Read more ...":extending.html#using_alternative_layouts
+
+
+h3.  Other
+
+* Buildr 1.3 upgrades to Rake 0.8, RSpec 1.1, RJB 1.1 and OpenJPA 1.0.1.  Buildr no longer includes or uses Facets.
+* JUnit tests now operate on all compiled test classes that extend @junit.framework.TestCase@ or use the @Test@ annotation; TestNG test cases are filtered by annotation.  Test cases no longer have to use a specific file name.
+* Remote repositories now support HTTP Basic Authentication.
+* The prepare task has been removed, if you need to, simply add a prerequisite to the compile task.
+
+
+h3.  Documentation
+
+* The "What's new?":whats_new.html page (this one, actually), summarizes all the important new features and changes in each release.
+* The "Recipes":recipes.html page (also available in the PDF) lists recipes for using Buildr, collected from the mailing list.  Feel free to contribute tips, tricks and techniques.
+* The "Troubleshooting":troubleshooting.html page (also available in the PDF) collects troubleshooting ideas from the mailing list.
+* The "Getting Started":getting_started.html has been rewritten to cover all you need to know about downloading and installing Buildr on Linux, OS X, Windows and with JRuby (1.1 or later).
+* A new "Contributing":contributing.html page has more details on how to file bugs, policy for submitting patches, running Buildr test cases, and helping with the documentation.
+* A new page for "Settings and Profiles":settings_profiles.html.
+* The "Extending Buildr":extending.html page that deals with writing your own tasks, creating extensions and specifying alternative layouts.
+* The site also includes "RSpec report":specs.html which provides the official specification against which we test each release.