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
Update to commons-io 2.11.0 #1138
Conversation
7a4cf09
to
6b58294
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CI pipeline failed after the PR was upgraded to the latest version from master
.
Could you fix the issues please?
0469d15
to
9d22105
Compare
9d22105
to
5304967
Compare
I rebased on latest master and fixed the issue. |
Thank you @guillaume-alvarez, I didn't have as much time as I hoped but I will definitely review it next week. Have a nice weekend! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you Guillaume, I finally reviewed this PR and had more time to research this issue with commons IO. It feels like those changes are related to a regression in the commons-io library: https://issues.apache.org/jira/browse/IO-754
I think we should follow the official recommendation and rely on accept(Path path, BasicFileAttributes attributes)
instead, to keep our logic in line with how the library has evolved.
Would you mind doing those changes please?
.../src/main/java/ro/isdc/wro/model/resource/locator/wildcard/DefaultWildcardStreamLocator.java
Outdated
Show resolved
Hide resolved
Hello @ppodgorsek, Do you want to keep it and change the accept method to override? |
Hello @kevinleturc , That's a very good point! Thank you for the information :) |
* Simplified the DefaultWildcardStreamLocator's file matching mechanism
A few tweaks have been made to the PR. Additionally, the builder pattern mentioned by @kevinleturc doesn't yet exist in commons-io 2.11.0, so a separate ticket (#1159) has been created to take care of this. (commons-io 2.13.0 introduces many other changes which break many tests, hence why it will be handled in a separate ticket) |
Thanks @guillaume-alvarez for your contribution! :) |
Fix #1136