Removing forced JUnit dep.

[jglick]

As http://stackoverflow.com/questions/7898446/how-to-exclude-a-dependency-from-parents-project-in-maven notes, it is impossible to remove a dependency specified in a parent POM. Generally a POM project just should not declare dependencies at all; it can use dependencyManagement where useful.

Affects jenkins-test-harness, which is trying to depend on JUnit 4.10 but is also stuck with this obsolete JUnit 3.8 from a parent.

[buildhive]

Jenkins » pom #2 SUCCESS
This pull request looks good
(what's this?)

[jglick]

Problem in e.g. jenkins-test-harness is that junit.* classes are in compile CP in 4.10 but test CP in 3.8. But due to the bad parent POM we cannot simply override junit:junit because we want junit:junit-dep in compile CP so as to avoid dumping random versions of Hamcrest classes in the CP. JUnit 4.11 will not suffer from this confusion: https://github.com/KentBeck/junit/pull/421

[buildhive]

Jenkins » pom #12 SUCCESS
This pull request looks good
(what's this?)

[jglick]

@kohsuke care to release this? Probably a prerequisite for moving to JUnit 4.11 in Jenkins trunk, which is valuable since it introduces predictable test case ordering within a suite even on Java 7 (which returns Class.declaredMethods in a random order).

[kohsuke]

1.30 released