Give InitializationError a useful message. JUnit itself does not use the message,
but having a useful message makes debugging runners easier.
InitializationError should make defensive copies
Remove outdated content in release notes about TestRule being abstract
Merge pull request #243 from kcooney/fix-release-notes

Remove outdated content in release notes about TestRule being abstract
Merge pull request #247 from kcooney/initialization-error-message

Give InitializationError a useful message
Fixes issue #219 where Assert.assertArrayEquals(float[],float[],float) displays an error message with doubles instead of floats
Added myself to acknowledgements.txt
Added test for issue #219
Actual exception added in ExpectedException

When using the ExpectedException to test for an exception to occur, it
throws an AssertionError when thrown exception does not match the
expected exception. Issue is however that in the JUnit runner results only
the actual exceptions message is shown and not the stacktrace. To fix
that, the actual exception is added to the cause of the AssertionError,
giving the exceptions in a format like:
java.lang.AssertionError: [reason]
  Expected: [expected exception]
     got: [actual exception + message]
 at [AssertionError stacktrace]
Caused by: [actual exception + message]
 at [actual exception stacktrace]
Actual exception added in ExpectedException

When using the ExpectedException to test for an exception to occur, it
throws an AssertionError when thrown exception does not match the
expected exception. Issue is however that in the JUnit runner results only
the actual exceptions message is shown and not the stacktrace. To fix
that, the actual exception is added to the cause of the AssertionError,
giving the exceptions in a format like:
java.lang.AssertionError: [reason]
  Expected: [expected exception]
     got: [actual exception + message]
 at [AssertionError stacktrace]
Caused by: [actual exception + message]
 at [actual exception stacktrace]
Merge branch 'master' of github.com:arjenw/junit
Reused HasWrongExpectedException instead of own defined class
(they were the same) and relocated the changes to a better location
in the file which is more inline with the rest of the file. And,
of course, removed the superfluous brackets.
Merge branch 'master' of github.com:arjenw/junit
Implemented the change now on org.junit.Assert.assertThat() as I think
that's a better place and has cleaner code than the original. Included
tests for both scenario's (assertThat as well as the ExpectedException).
* Removed empty line in ExpectedException
* Moved CauseMatcher to ResultMatchers and splitted it up in two
matchers (failureIs and causedBy)
* Added tests for both matchers
added an 'expectCause(Throwable cause)' to the ExpectedException rule
Upgrade to Hamcrest 1.3.0 RC2

- Matchers in JUnitMatchers that are now provided by hamcrest-core are deprecated
- Using CoreMatchers where possible

*Important:*
In some but not all cases, this change will cause compiler errors for people
using JUnitMatchers.hasItem(s), both(), and either().
Remove test for functionality provided by Hamcrest
Remove deleted BothTest from AllTests
Simplify matcher expression in ParameterSignatureTest