...
- Motivation:
- Security reasons: lots of dependencies that were with vulnerabilities issues had the newer version developed with Java 17 as minimum version, like Spring Fmwk.
- Jakarta EE upgrade from Javax
- Deprecation on Junit4
- Improve benchmarks for application usage
- Challenges:
- main challenge was to match servlet dependencies with the Jakarta EE version of things. Most dependencies created a new groupId or artifactId for retro compatibility.
- dependencies that hadn't changed yet from javax.* to jakarta.*
- too many options, but very few documentation from OpenAPI/Swagger on the upgrade. (just a flag useJakarta that wasn't in any document)
- override dependencies from oparent
- java17 changes on reflection and closed access to java basic packages caused some issues with unit tests and clm jobs
- Tools:
- intellij was very useful with the function to migrate junit4 to junit5. paid version also can help with jakartaEE migration
- nexusIQ plugin helped when testing which next version would be the best (less breaking code changes and less/none vulnerabilities)
Slides & Recording
...
| title | YouTube |
|---|
...
Agenda
...
- Point 1
- Point 2