-
Notifications
You must be signed in to change notification settings - Fork 493
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
8305 Upgrade to Jakarta EE 10 and Payara 6 #9116
Conversation
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.
For now this is payara-6.2022.1.Alpha2 (the latest).
update docker-aio for Payara 6 #8305
The jars were built from this commit (scratch work): pdurbin/rewrite@d494160
Conflicts (just javax vs. jakarta imports): src/main/java/edu/harvard/iq/dataverse/TemplatePage.java
…22.1.Alpha2.zip
#8305 Vagrantfile.payara6 deploys 8305-payara6 warfile on payara-6-A2
Also, in docker-aio, restore lines to publish root dataverse collection (uses SWORD, known to be broken) and grant perms. Also update scripts and config related to installer or dev environments.
Otherwise, at runtime, SWORD APIs fail (and who knows what else). Note that CDI 4.0 is coming with Jakarta EE 10 and we'll need to switch to "annotated" then.
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.
Conflicts (all javax vs jakarata): src/main/java/edu/harvard/iq/dataverse/EditDatafilesPage.java src/main/java/edu/harvard/iq/dataverse/UserNotification.java src/main/java/edu/harvard/iq/dataverse/UserNotificationServiceBean.java src/main/java/edu/harvard/iq/dataverse/api/Notifications.java src/main/java/edu/harvard/iq/dataverse/api/datadeposit/MediaResourceManagerImpl.java src/main/java/edu/harvard/iq/dataverse/authorization/providers/builtin/DataverseUserPage.java src/main/java/edu/harvard/iq/dataverse/authorization/users/AuthenticatedUser.java src/main/java/edu/harvard/iq/dataverse/util/FileUtil.java src/main/java/edu/harvard/iq/dataverse/util/json/JsonPrinter.java src/test/java/edu/harvard/iq/dataverse/util/json/JsonPrinterTest.java
Note that we need to swap Payara 6.2022.1.Alpha2 for the final version.
Backlog grooming:
|
sizing:
|
Phil has started keeping track of the work needed for this in Spike: Upgrade to Payara 6 and from EE 8 to EE 10 (end of Payara 5 Community Edition security patches Q2/2022) so this issue is no longer being used as described. I've created a new temporary column Upgrade to "Jakarta EE 10 and Payara 6" and added this there. |
Sizing:
Notes
Next steps:
|
Please be aware that the last merge was not correctly executed! It is no easy task to merge this because of the Jakarta EE switch! This is at least a size 10 task, as the last merge needs to be reverted as well! |
|
This appears to be a flawed PR. |
See related: #8305 |
I'm trying to install the latest version of IQSS Dataverse, 5.13: Dataverse 5.13 installation recommends Payara 5.2022.3, but it cannot be downloaded:
What can be done in this case? |
@diego-guillen please see #9638. Your question is beyond scope for this PR 😉 |
I am going to close this pull request now, as we will operate on a new branch and a new pull request for the actual move for Payara 6 after the release of Dataverse 5.14. See #9685 for the successor PR. |
What this PR does / why we need it:
Payara 5 is going EOL for community usage (= without a payed support contract). Payara 6 is the successor, but allows to use Jakarta EE 10 only.
Which issue(s) this PR closes:
Special notes for your reviewer:
Do not move this to QA until we've made a final decision to go with the Rewrite/PrettyFaces library I built on my Mac and put inlocal_lib
. Check EE9 Compatible Release ocpsoft/rewrite#304 for progress toward a compatible release from upstream.attachment;
for the user if it isn't supplied?Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No
Is there a release notes update needed for this change?:
Yes, a stub is included.
Additional documentation:
None but references in the guides to Payara 5 have been switched to Payara 6.