-
Notifications
You must be signed in to change notification settings - Fork 357
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
Public class removed in bugfix release? #5720
Comments
I agree that we did not need to remove that class. On the other hand, that is an internal package which may be a subject of a change between versions. I do not see a reason why not to put it back for 3.x |
It's not like I'm using it in my code. Something else is probably invoking it via an older jersey package, but commons got upgraded by something else. The upshot is dropping in your new bugfix version can blow up a project, and reverting resolves the issue. If that's ok then... I guess it's ok. I'll just fiddle with my dependencies and force it not use your new version. |
Ah I see I failed at parsing the double negative above. Thanks for fixing this. |
Seeing as Jersey 3.1.x is on JDK11, note that there is a JDK built-in replacement for NullOutputStream. |
Yes, that's why it has been removed. But the customers are used to utilize Jersey NullOutputStream which is for some reason public. |
21668db#diff-77ffb7eeac2f33be75d8debb4d32cd5fee7f815ab48603081e7a2a35d3d1fdbd
NullOutputStream was removed which means when gradle tries to substitute the highest version among several dependencies one can get java.lang.ClassNotFoundException errors for this... super irritating, and forcing me to backtrack to 3.1.6 instead of 3.1.7.
Removing public classes is not a typical thing for bugfix releases, and doesn't seem to fit the "3.1 compatible release" phrase.
The text was updated successfully, but these errors were encountered: