pom file update to build XOAI-5.0.0 #9339 #9354
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
As described in the linked issue, switching the application to the long-awaited final version of the XOAI v.5.0.0 that has just been released.
Which issue(s) this PR closes:
Closes #9339
Special notes for your reviewer:
This uses the final, mature version of XOAI 5.0.0. It contains the latest changes, that were added to accommodate the PR #9310. Those were tested as part of the QA on that PR (built with the final release candidate version, essentially the same jars but packaged as dev. snapshots. The original plan was to wait for the 5.0.0 to be packaged before merging it, but then we merged it anyway; kind of by accident, but in retrospect, it would look bad for that PR to sit in QA all this time).
The XOAI release in question is the mature version, and the culmination of all the work done to improve, update and modernize the library since it was forked off DSpace/xoai and moved into its new home at https://github.com/gdcc/xoai. Massive credit goes to @poikilotherm for making it happen and all the work he's done there.
Suggestions on how to test this:
Functionality-wise, almost everything in this PR has gone through our QA process already. So it may only need a quick glance, confirming that nothing is visibly broken and the integration tests are passing.
The only small change/improvement you will notice is the treatment of
yyyy-mm-dd
dates (the thing you noticed during QA of #9316)Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: