Starting to get rid of deprecation warnings
Get rid of MethodRule deprecation warnings
Renamed TestRuleTestWatchman to TestWatcher, updated docs
Create MultipleFailureException in org.junit.runners.model and deprecate the one in org.junit.internal.runners.model.
Update MultipleFailureException to have a useful message.

This allows developers who write custom runners to properly handle multiple exceptions without depending on internal classes.
TODO cleanup for 4.9 lead-up
further documentation cleanup, especially around TestRule
Update JUnit version, improve ClassRule javadoc, update release notes
Further documentation updates.  No obvious changes from 4.8.2 missing, now.
Remove obsolete file Listed.java
Update build_tests.sh to test "ant profile"
Update version in pom.xml; delete obsolete SuiteBuilder.java;
remove duplication in build.xml
Fix build.xml with better macro usage
For consistency, renaming version to 4.9b1
Fix typos in comments
Make TestRule an abstract class. Specify target of the rule annotations.

Making TestRule abstract allows the apply method to be non-public, so
developers with IDEs that are using rules will not see the apply method
as a valid completion.
Add runLeaf() to ParentRunner.
This makes it easier to write a custom runner that supports
MultipleFailureException and AssumptionViolatedException
without depending on internal classes.
removing redundant asserts
Fixed a javadoc problem.  More remain.
Fix bad javadoc and bad release notes
Merge branch 'run-leaf' of https://github.com/kcooney/junit into kcooney-run-leaf

Conflicts:
	src/main/java/org/junit/rules/TestRule.java