NoSuchMethodError for computeIfAbsent in SpringExtension after upgrade to 7.0.0 version

[rakeshreddygundala-ai]

After we upgrade to 7.0.0 version for org.springframework.spring-test , we are getting NoSuchMethodError for computeIfAbsent().

Our tests are failing at moment after we upgrade this to latest version.

java.lang.NoSuchMethodError: 'java.lang.Object org.junit.jupiter.api.extension.ExtensionContext$Store.computeIfAbsent(java.lang.Object, java.util.function.Function, java.lang.Class)'
        at org.springframework.test.context.junit.jupiter.SpringExtension.getTestContextManager(SpringExtension.java:412)
        at org.springframework.test.context.junit.jupiter.SpringExtension.beforeAll(SpringExtension.java:170)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
        Suppressed: java.lang.NoSuchMethodError: 'java.lang.Object org.junit.jupiter.api.extension.ExtensionContext$Store.computeIfAbsent(java.lang.Object, java.util.function.Function, java.lang.Class)'
                at org.springframework.test.context.junit.jupiter.SpringExtension.getTestContextManager(SpringExtension.java:412)
                at org.springframework.test.context.junit.jupiter.SpringExtension.afterAll(SpringExtension.java:181)
                ... 1 more

Please help on fix it and provide a solution for this problem.

Thank You.

[bclozel]

This missing method has been introduced in JUnit 6.0. Are you using JUnit 6.0 as required by the new baseline?

[Gugu7264]

This missing method has been introduced in JUnit 6.0. Are you using JUnit 6.0 as required by the new baseline?

I'm curious, why isn't the wiki page linked in the release? Release doesn't mention any breaking change or anything and everything is hidden in that wiki page :/

[bclozel]

I'm curious, why isn't the wiki page linked in the release? Release doesn't mention any breaking change or anything and everything is hidden in that wiki page :/

I have just added a link to the release notes in the GitHub release. Hopefully this will help. The 7.0 release on GitHub only highlights changes that were committed after the previous candidate release.

I wouldn't say we are "hiding" content in a wiki page, given that we've been consistently linking to that page in all blog posts announcing all the 7.0 milestone releases this year (RC1, M9, etc), including the main announcement blog. We do maintain that information on a wiki page because we are consistently updating it after the release (even months after, when the community reports feedback about their upgrade experience) - and also because that's what the community has been using for years.