fix: Mockito inline mocking for Java 21+ #207
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this fix the execution of the maven surefire plugin with Java 21 logged warnings that mockito should be added as a java agent, because the self-attaching won't be supported in future java releases.
In Java 24 the test just broke.
This problem is solved by modifying the
pom.xml
of the parent and doing this changes:surefireArgLine
from the properties. This can be added back when it's needed (for example if JaCoCo will be used).Furthermore, the
pom.xml
in themcp-spring-*
modules now have the byte-buddy dependency included, as the test would otherwise break when trying to mockMcpSchema#CreateMessageRequest
.Motivation and Context
This is a fix for #187
How Has This Been Tested?
I executed
mvn clean package
with Java 17, 21 and 24 and checked for the warning and whether the modules can be built.Types of changes
Checklist