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

Request: New Maven release for Junit dependency scope change #131

Open
Macil opened this issue Jul 12, 2018 · 4 comments
Open

Request: New Maven release for Junit dependency scope change #131

Macil opened this issue Jul 12, 2018 · 4 comments

Comments

@Macil
Copy link

Macil commented Jul 12, 2018

A commit 5 years ago (7ae9400#diff-600376dffeb79835ede4a0b285078036) fixed it so that json-simple only depends on Junit in the test scope, but there have been no releases since that fix. Could a new release be made at least for that?

I frequently work on projects that don't use Junit 4.10 but depend on libraries that depend on json-simple which then pulls in Junit 4.10, and then IDEs annoyingly auto-suggest Junit 4.10 annotations whenever we write tests even if we use a different test system. It's easy to pick a Junit 4.10 @Test annotation instead of our own test system's annotation and accidentally make a test that never runs without realizing it. It's a little silly issue since projects can be configured to exclude the Junit subdependency, but I see a lot of projects fail to do that, and the fix for them all has been sitting unused and ready for 5 years. I don't think you should worry that the scope change fix is too small for a release: it's better to have it out eventually, and there's no shortage of possible version numbers.

@oscerd
Copy link

oscerd commented Aug 5, 2020

I think a release is needed, just for leaving a definitive released without junit as runtime dep

@chkpnt
Copy link

chkpnt commented Apr 29, 2021

+1

@rcrlik
Copy link

rcrlik commented May 3, 2021

+1

Any update on this?

@Lonzak
Copy link

Lonzak commented Sep 20, 2024

+1 Please release a new version.
(or reflect the project status and set it to archive / not maintained anymore)

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

No branches or pull requests

5 participants