Ban JUnit 4 imports#190
Merged
asimell merged 1 commit intojenkinsci:developmentfrom Oct 26, 2025
strangelookingnerd:patch-1
Merged
Ban JUnit 4 imports#190asimell merged 1 commit intojenkinsci:developmentfrom strangelookingnerd:patch-1
asimell merged 1 commit intojenkinsci:developmentfrom
strangelookingnerd:patch-1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ban JUnit 4 imports
To prevent regressions when adding new tests, jenkinsci/plugin-pom#1178 introduced a new flag that enables a Maven Enforcer rule banning
org.junit.*imports while allowingorg.junit.jupiter.*.With this change, the build will fail if any
org.junit.*imports are introduced.Testing done
None. Rely on
ci.jenkins.io.Submitter checklist