-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
jersey-media-multipart depends on JUnit - regression #5226
Milestone
Comments
benken-parasoft
added a commit
to parasoft/parabank
that referenced
this issue
Dec 29, 2022
A quick grep thru the Jersey source code, and it appears |
This was referenced Feb 17, 2023
1 task
1 task
This was referenced Mar 16, 2023
This was referenced May 11, 2023
1 task
This was referenced Jun 1, 2023
This was referenced Jun 4, 2023
This was referenced Jun 15, 2023
This was referenced Jul 6, 2023
This was referenced Aug 28, 2023
1 task
This was referenced Jan 16, 2024
1 task
This was referenced Apr 13, 2024
Closed
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
After upgrading from Jersey 2.37 to 2.38, my project's main sources started building against JUnit Jupiter which is now getting pulled in as a transitive dependency of jersey-media-multipart. The JUnit dependency in the pom for jersey-media-multipart is missing
<scope>test</scope>
.The pom for jersey-media-multipart 2.38 has this:
The pom for jersey-media-multipart 2.37 is also missing test scope:
Even though "test" scope is missing in 2.37, this problem was not visible in 2.37 because dependencyManagement for org.glassfish.jersey:project forced test scope:
In 2.38, dependencyManagement for org.glassfish.jersey:project now imports the JUnit BOM (which is good):
So, now that the JUnit BOM is imported, any projects missing "test" scope for junit-jupiter need to be corrected. I noticed this for jersey-media-multipart but didn't check if any other Jersey modules also have the same issue.
As a workaround, I have to force an exclusion in my project's pom:
The text was updated successfully, but these errors were encountered: