-
Notifications
You must be signed in to change notification settings - Fork 416
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
Dependency updates for mapstore-services and POMs refactoring #10015
Conversation
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.
@afabiani we have opened this PR to contribute what you have done for c125-2024.01.xx branch in master. Some conflicts have been fixed as well.
Can you please double check the PR? Can you also please explain better the purpose of this contribution?
There are many failing checks.
@tdipisa the purpose was to cleanup the poms mess and update the dependencies. Main goal was to avoid spreading and duplicating the properties around and have the dependencies coherent among the modules. Unfortunately the conflicts resolution was not good here you it has broken all the poms inheritance. I will send a fix for that. |
Bump version of print-lib to 2.4-SNAPSHOT Bump version of http_proxy to 1.6-SNAPSHOT
Done |
@offtherailz this PR should be backported to 2024.01.xx but using versions (of geostore, proxy, services and print) expected for the stable branch. The backport should be done only after functional tests. Other backports are necessary: |
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.
I'm going to apply my changes and test.
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.
I should have fixed all the workflows on github to work with your changes. Hope this could simplify updates and a lot of troubles in our future work. 🤯
Description
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#
What is the new behavior?
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information