-
Notifications
You must be signed in to change notification settings - Fork 69
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
Issue-1860: Update commons-fileupload:commons-fileupload from 1.3.3 to 1.4 #115
Conversation
This will be reverted after child modules have been successfully built and tested.
Hi! Thank you for your contribution! Would you mind signing the ICLA, as described in the Contributing page? Also, please, feel free to join our chat channel, if you'd like to learn more about the project and/or like to find out what else you could help with. Kind regards, Martin |
This reverts commit 4f2980b and sets the version back to the normal 1.0-SNAPSHOT.
Signed, sent and reverted. |
Thank you! Congratulations on your first pull request! :) |
As a follow-up task, could you please check, if this upgrade also works for the strongbox |
I take it that I have to build said branch for strongbox-db myself, as the PR-19 version is not deployed, is it? |
Sounds about right. |
Branch issues/1649 still compiles and |
Do you want anything else done with that? I don't think you want the change on branch Man, the integration tests run really long on this branch. |
Thanks for checking this! No need for further pull requests, or rebasing. |
Pull Request Description
This pull request closes strongbox/strongbox#1860
Acceptance Test
strongbox-parent
withmvn clean install
still works.strongbox
project withmvn clean install -Dintegration.tests
still works.mvn spring-boot:run
in thestrongbox-web-core
still starts up the application correctly.strongbox-distribution
from azip
ortar.gz
still works.strongbox-web-integration-tests
still run properly.Questions
Does this pull request break backward compatibility?
Does this pull request require other pull requests to be merged first?
Does this require an update of the documentation?
Code Review And Pre-Merge Checklist