Add support for JUnit 4.11

[GoogleCodeExporter]

Attached patch adds support for JUnit 4.11.

Original issue reported on code.google.com by steven.n...@gmail.com on 31 Jan 2013 at 2:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Idiot...

Original comment by steven.n...@gmail.com on 31 Jan 2013 at 2:06

[GoogleCodeExporter]

Should we also remove the nodeps configuration as per 
https://github.com/KentBeck/junit/blob/master/doc/ReleaseNotes4.11.md#maven-arti
facts ?

"Maven artifacts

Up until now there were two Maven artifacts for JUnit: junit:junit-dep and 
junit:junit. From a Maven point-of-view only the former made sense because it 
did not contain the Hamcrest classes but declared a dependency to the Hamcrest 
Maven artifact. The latter included the Hamcrest classes which was very 
un-Maven-like.

From this release on, you should use junit:junit which will be what 
junit:junit-dep used to. If you still reference junit:junit-dep, Maven will 
automatically relocate you to the new junit:junit and issue a warning for you 
to fix."

Original comment by grumpyja...@gmail.com on 31 Jan 2013 at 4:17

[GoogleCodeExporter]

Yes, I think we should.

Original comment by steven.n...@gmail.com on 31 Jan 2013 at 4:34

[GoogleCodeExporter]

Done.

Original comment by steven.n...@gmail.com on 31 Jan 2013 at 4:46

Attachments:

• add-junit-4.11-NEW.diff

[GoogleCodeExporter]

Thanks, added in r394.

FYI, removed "default" configuration, as this is the "default" when none are 
given.

Original comment by archie.c...@gmail.com on 4 Feb 2013 at 2:38

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Oops, meant "added in r2569".

Original comment by archie.c...@gmail.com on 4 Feb 2013 at 2:38