Upgrade the Spring TestContext Framework to JUnit 4.7 [SPR-5963]

[spring-projects-issues]

Sam Brannen opened SPR-5963 and commented

Depends on: https://issuetracker.springsource.com/browse/EBR-435

---

Affects: 3.0 M4

Issue Links:

• JUnit 4.5 support broken [SPR-5995] #10663 JUnit 4.5 support broken

Referenced from: commits 4263858

[spring-projects-issues]

Neale Upstone commented

Hi,

Using JUnit 4.5, 4.6 and now 4.7 while tracking the Spring 3 milestones is proving to be ... interesting.

I've just tried 4.7 with Spring 3.0.0.M5, and Junit has made formerly public methods private.

4.6 and 4.7 seem to break historical public interfaces, which then means that Spring is having to be adapted. Do you have any indication from the JUnit people that when Spring 3.0.0 is released, that it won't, yet again, break the Spring code?

Naturally, under an OSGi runtime it's not an issue, but for those not using OSGi, we can only have one JUnit on the classpath.

[spring-projects-issues]

Sam Brannen commented

Neale,

See the linked issue (#10663) for further details regarding JUnit 4.5, 4.6, and 4.7.

Do you have any indication from the JUnit people that when Spring 3.0.0 is released, that it won't, yet again, break the Spring code?

No, we do not yet have any such indication from the JUnit team, but I am working on it. ;)

Regards,

Sam