Fix DockerAvailableCondition compilation error with JUnit Jupiter 6.0.0 #159
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.
Problem
The
DockerAvailableCondition
class was failing to compile with the following error:Root Cause
The
evaluateExecutionCondition
method was defined with a nullableExtensionContext?
parameter, but theExecutionCondition
interface in JUnit Jupiter 6.0.0 requires a non-nullableExtensionContext
parameter. This signature mismatch prevented the method from properly overriding the abstract method from the interface.Solution
Changed the parameter type from nullable to non-nullable to match the interface signature:
Testing
This is a minimal fix that only changes the parameter nullability to align with the JUnit Jupiter API requirements.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.