Implemented a file parser. Added SourceOfExamples for lazy example listing (especially useful when lazily searching for files that match a certain prefix).
Ported the file search with pre-Java 7 API.
Overloaded the the fileParser method. Renamed SourceOfExamples to ExampleSource. Documented fileParser, FileExamples, and ExampleSource.
Moved ExampleSource into a separate file.
Documented the new Parsers API a bit. Prepared the new API so that we can port the old ones to the new. Added support for filtering erroneous examples.
Documented the DynamicExamples and FixedSetExamples classes.
Now using ExampleSource in collection-based completion parsers. Removed the Examples parser. Renamed DynamicExamples to ParserWithExamples.
Created unit tests for ParserWithExamples and FixedSetExampleSource.
Improved the description of ParserWithExamples tests.
Added tests for FileExamples. Improved the file-searching in FileExamples.
Initial Spanish translation of documentation
Merge remote-tracking branch 'remotesbt/0.13' into 0.13
Reintroduced the `examples` method. Reintroduced and deprecated the `checkMatches` method.
Use dedicated api for lastCompilationTime in build definition

Since sbt 0.13.0, we have dedicated API in Analysis that gives access to
information about all compilations performed since the last time clean
was ran.

By looking at at last compilation we can determine lastCompilationTime
value.

Fixes #1272
Merge pull request #1273 from gkossakowski/lastCompilationTime

Use dedicated api for lastCompilationTime in build definition
Automatically run GC/finalization after each task execution.

Fixes #1223.

* Add a new key to disable forcing the garbage collector to run
  after each task-executioin
* Add a new flag to disable forcing the garbage collector to run
  after each task-exeuction
* Add a hook into EvalauteTask to run System.gc/System.runFinalization
  after each task execution

Review by @eed3si9n
Added a test reporter for JUnit XML

Taken from https://github.com/chenkelmann/junit_xml_listener and slightly improved.
Activating is now just a matter of setting `testReportJUnitXml` to true.
This not only brings a very handy feature (hudson/jenkins support that syntax),
but gives more options for testing the SBT test infrastructure.
For instance checking that the test output is well segregated during a parallel
test run is just a matter of checking the report output.

Conflicts:
	main/src/main/scala/sbt/Keys.scala
Migrate JUnitXmlReport into an autoplugin.
Separate location of analysis cache if we're cross compiling scala.

* Add task to determine file-name of analysis cache
* If crossPaths := true, then add scala binary version to the analysis cache name.

This makes it possible to leverage incremental compilation with the `+` command.

Fixes #1267
Remove enabling key for JunitXmlReportPlugin.

This migrates JunitXmlReportPlugin to work the way we desire
new sbt features/plugins to work:

* Enabling the feature is having the plugin available.
* Disabling the feature is disabling the plugin
* All code/settings for the feature are isolated to the plugin.