Merge v6.0 into master #9896
Merged
Merge v6.0 into master #9896
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. The Jersey dependencies in use did not use the versions imported via the Payara BOM (which itself imports a Jersey BOM). 2. The coordinates for the server package changed, re-aligned.
…nly #8305 This avoids potential trouble were it's unclear from where the higher exceptions come from, javax or jakarta namespace.
Also add provided dependency of our persistence provider to POM to allow class resolution in IDEs.
Many projects have moved to Eclipse foundation, have been replaced or renamed with the move to Jakarta EE 10. With the import of the new EE 10 Payara BOM, we need to follow their changes (or provide the deps on our own).
As the SPI module used Java EE, we need to release a v2, as the move to Jakarta EE is a breaking change.
Removing some rogue usages of OcpSoft PrettyFaces internal utils for String care and replacing with either Apache Commons Lang3 or native JVM code.
…8305 Any users registered before 2021 release to oss.sonatype.org. As gdcc was installed after that, we only had s01.oss.sonatype.org. Also enabling both snapshot repos for Rewrite and SWORD2 See also https://central.sonatype.org/news/20210223_new-users-on-s01
…8305 This is due to the fact that Payara 6 Servlets are more strict in their parsing of HTTP headers.
In EditDDI I was seeing a NullPointerException on line 136 (createNewDraftVersion). Switch from `@Context HttpServletRequest` to our ordinary way of API auth fixed it. In DataversesIT I was seeing an OptimisticLockException so I added a sleep.
Involves Jakarta Faces 4.0 and Servlet 6.0
The backing bean actions were attached to normal "<a>" elements, which means they were executed on page load and not, as expected, via JavaScript onClick. Former versions of JSF were less strict, now we need to use the standard compliant "<h:commandLink>"
…page is in create mode. #9825
switch to UNF 6.0 on Maven Central
explain how to release to Maven Central (and mention npm)
A quick xhtml-only fix for the "template with custom terms of use" bug
support Postgres versions 14 and 15
Co-authored-by: Oliver Bertuch <[email protected]>
create 6.0 release notes
bump version to 6.0
This comment has been minimized.
This comment has been minimized.
1 similar comment
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
merge into master.