Upgrade to Payara 7 and Java 21

[qqmyers]

What this PR does / why we need it: This PR updates Dataverse to be compatible with Payara 7.2025.2 and Java 21. Aside from the doc changes (payara6 -> payara7 etc.) the changes were relatively minor - a couple deprecated annotations we use (NotEmpty, NotBlank) were removed and replaced with new ones, and some of the EE related classes we mock in tests now have a few more methods that have to be overridden.

Which issue(s) this PR closes:

• Closes Payara 6 community edition has reached its End Of Life #12020
• Closes bump to OpenJDK 21 #11585

Special notes for your reviewer: Someone will need to check the Docker related compose files and documentation to make the relevant updates to Payara and Java. I tried to avoid updating things related to the Keycloak container since it shouldn't need to update to Java 21.

Suggestions on how to test this: Undeploy the current Dataverse, install Payara 7.2025.2 and Java 21, deploy this branch, regression test.

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?: included.

Additional documentation:

[coveralls]

coverage: 24.336%. remained the same
when pulling df2fd0a on QualitativeDataRepository:IQSS/12020-Payara7_Java21_update
into 9a5ca93 on IQSS:develop.

[qqmyers]

Apparently Payara 7.x has a minor bug - any API call with a colon in it fails. payara/Payara#7777 - looks like we need to wait for 7.2025.3 or 7.2026.1 +

[qqmyers]

Apparently Payara 7.x has a minor bug - any API call with a colon in it fails. payara/Payara#7777 - looks like we need to wait for 7.2025.3 or 7.2026.1 +

There's been an unofficial report that this is fixed in 7.2026.1 - can now move forward and try that.

[wshahn]

TASK [dataverse : copy warfile over release] ***********************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Source /opt/dataverse/dataverse/target/dataverse-6.8.war not found"}

@qqmyers Hit this when building the warfile, could you please refresh your branch when you get a chance? Thanks!

[wshahn]

Tests passed:

[stevenwinship]

@qqmyers please resolve the conflicts

[pdurbin]

A quick review.

[pdurbin]

I'm just using this comment to jot down expected error messages if you don't follow the upgrade steps.

mvn -Pct clean package docker:run
...
[ERROR] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[ERROR] Detected JDK version 17.0.16 (JAVA_HOME=/Users/pdurbin/.sdkman/candidates/java/17.0.16-tem) is not in the allowed range [21.0,).
...
[ERROR] DOCKER> Unable to pull 'gdcc/base:6.10-noble-p7.2026.1-j21' : {"message":"failed to resolve reference \"docker.io/gdcc/base:6.10-noble-p7.2026.1-j21\": docker.io/gdcc/base:6.10-noble-p7.2026.1-j21: not found"} (Not Found: 404) [{"message":"failed to resolve reference \"docker.io/gdcc/base:6.10-noble-p7.2026.1-j21\": docker.io/gdcc/base:6.10-noble-p7.2026.1-j21: not found"} (Not Found: 404)]

[pdurbin]

I was able to get the branch running in Docker after switching to Java 21 and building the base image myself. I made a couple commits in the docs about this:

24cad02 build the base image yourself for new Payara versions
64b6187 explain sdk use

I was able to create a dataset.

[pdurbin]

The above is just a placeholder, obviously. We should take a look at these:

• add upgrade instructions for Payara 5 to 6 #9774
• https://github.com/IQSS/dataverse/releases/tag/v6.0

[pdurbin]

Suggested change

default-web.xml

[pdurbin]

For default-web.xml, copy it over but put in the changes we need.

[pdurbin]

Note to self, we'll be copying the old domain1 directory, like we did at #11827 and https://github.com/IQSS/dataverse/releases/tag/v6.9

[qqmyers]

-Djakarta.security.jacc.policy.provider=org.glassfish.exousia.modules.def.DefaultPolicy should also be added. These are both in the .