You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: