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

Fix #168: Commons-IO signatures fails to resolve in commons-io v2.7 #169

Merged
merged 2 commits into from
Jun 3, 2020

Conversation

uschindler
Copy link
Member

@uschindler uschindler commented Jun 3, 2020

This is caused by an incompatible change in commons-io 2.7 (ByteBufferOutputStream was refactored to have a new base class AbstractByteBufferOutputStream); This also adds signatures for version 2.7.

…as there was an incompatible change; This also adds signatures for version 2.7.

TODO: Scan for other API differences (new methods) in 2.7 vs. 2.6
@uschindler uschindler mentioned this pull request Jun 3, 2020
@uschindler uschindler self-assigned this Jun 3, 2020
@uschindler uschindler added this to the 3.0.1 milestone Jun 3, 2020
@uschindler uschindler linked an issue Jun 3, 2020 that may be closed by this pull request
@uschindler uschindler merged commit f5c3f88 into master Jun 3, 2020
@uschindler uschindler deleted the dev/issue168 branch June 3, 2020 17:58
uschindler added a commit that referenced this pull request Jun 3, 2020
Commons-IO signatures fails to resolve in commons-io v2.7, as there was an incompatible change; This also adds signatures for version 2.7 (a new abstract class that caused this issue).

In a later version of forbiddenapis there will be a more robust fix for this (resolving virtual methods during signatures parsing)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Support commons-io 2.7
1 participant