Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jersey-media-multipart 2.38 has compile dependency to junit-jupiter #5238

Closed
i23098 opened this issue Jan 21, 2023 · 2 comments · Fixed by #5229
Closed

jersey-media-multipart 2.38 has compile dependency to junit-jupiter #5238

i23098 opened this issue Jan 21, 2023 · 2 comments · Fixed by #5229

Comments

@i23098
Copy link

i23098 commented Jan 21, 2023

Version 2.38 has compile dependency to junit-jupiter - https://mvnrepository.com/artifact/org.glassfish.jersey.media/jersey-media-multipart/2.38

Looking at 2.37 that used older junit, it has junit as a test dependency - https://mvnrepository.com/artifact/org.glassfish.jersey.media/jersey-media-multipart/2.37

junit-jupiter should be a test dependency.

@i23098
Copy link
Author

i23098 commented Jan 21, 2023

Looking at the pom file using tag 2.38, the scope is missing... https://github.com/eclipse-ee4j/jersey/blob/2.38/media/multipart/pom.xml

Looking at master, it has the <scope>test</scope> https://github.com/eclipse-ee4j/jersey/blob/master/media/multipart/pom.xml added in 3b182eb

Does this mean in 2.39 it will be correct (or the change needs to go to some other branch(es) as well)?

@i23098 i23098 changed the title jersey-media-multipart has compile dependency to junit-jupiter jersey-media-multipart 2.38 has compile dependency to junit-jupiter Jan 21, 2023
@senivam senivam linked a pull request Jan 23, 2023 that will close this issue
@senivam
Copy link
Contributor

senivam commented Jan 23, 2023

fixed by #5229

@senivam senivam closed this as completed Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants