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
Adding assertNotEquals to Object, long and double
Added test for issue #219
Fixes gh-121 (ExpectedException handles JUnit exceptions)

ExpectedException rule no longer handles AssertionErrors and
AssumptionViolatedExceptions by default. This means that the
rule doesn't intercept if your test fails because of an violated
assertion or assumption.

If you want to test assertions or assumptions you have to tell
the rule to handle such exceptions via handleAssertionErrors()
or handleAssumptionViolatedExceptions().
deleted duplicate EventCollector
the two handle... methods are returning the rule

The two methods handleAssertionError() and
handleAssumptionViolatedExceptions() are returning the rule.

Now you can write
  @Rule
  public ExpectedException thrown = none().handleAssertionError();
or
  @Rule
  public ExpectedException thrown = none().handleAssumptionViolatedExceptions()

Thank you David, for this suggestion.
Fix for #359
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
Added MainRunner. This removes the need for public methods in JUnitCore
MainRunner installs a SecurityManager which traps the System.exit(), thereby
removing the need to have runMainAndExit and runMain public in JUnitCore.
MainRunner is only used in the tests of course.
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).