Upgrade Jersey from 2.28 to 2.43 in parent/pom.xml

Description

This is Phase 2 of the Jersey upgrade initiative (parent issue #33857). After completing the Base64 migration (issue #33859), we can now safely upgrade Jersey from version 2.28 to 2.43 to enable Java 21 and 25 bytecode support.

Objective

Update Jersey version in parent/pom.xml from 2.28 to 2.43, which will automatically bundle ASM 9.7 for Java 21/22/23 support.

Prerequisites

• Issue #33859 must be completed and merged (Base64 migration)
• All Jersey internal API usages must be removed
• Authentication and API token functionality verified working

Implementation

File to Update

parent/pom.xml - Update Jersey version property:

• Current: 2.28
• Target: 2.43

What This Enables

• ASM 9.7 (bundled with Jersey 2.43)
• Java 21 bytecode support
• Java 22 bytecode support
• Java 23 bytecode support
• Foundation for future Java 25 support (will need ASM 9.8+)

Jersey Version Details

Jersey 2.43 includes:

• ASM 9.7 repackaged internally
• Full Java 21/22/23 support
• All existing Jersey 2.x APIs maintained
• No breaking changes from 2.28

Testing Requirements

• All JAX-RS REST endpoints function correctly
• Authentication flows work (HTTP Basic Auth, API tokens)
• OSGi bundles load and function properly
• Plugin system works with new Jersey version
• Full integration test suite passes
• Postman test collections pass
• No runtime errors related to ASM or bytecode compatibility

Validation Steps

1. Update version in parent/pom.xml
2. Clean build: ./mvnw clean install -DskipTests
3. Run targeted integration tests: ./mvnw verify -pl :dotcms-integration -Dcoreit.test.skip=false -Dit.test=ContentTypeAPIImplTest
4. Run full test suite
5. Test in Docker: just dev-run
6. Verify REST API endpoints work
7. Check OSGi bundle loading
8. Verify plugin compatibility

Rollback Plan

If issues arise, revert parent/pom.xml to Jersey 2.28. The Base64 migration (Phase 1) is compatible with both versions.

Related Issues

• Parent Epic: #33857 - Upgrade Jersey and ASM to support Java 21 and 25
• Prerequisite: #33859 - Migrate Jersey internal Base64 to java.util.Base64 (must merge first)
• Next Phase: Java runtime upgrade to 21

Technical Context

• Jersey repackages ASM internally as jersey.repackaged.org.objectweb.asm
• No separate ASM dependency needed in pom.xml
• Stays on Jersey 2.x (javax namespace) - no Tomcat 10 migration required yet
• Jersey 3.x upgrade (jakarta namespace) blocked until Tomcat 10 migration

Acceptance Criteria

• [Define what needs to be accomplished]

Additional Notes

[Any additional context or notes]

Start by confirming prerequisite issue #33859 is merged, then inspect the Jersey version property in parent/pom.xml. Update the version from 2.28 to 2.43 and run ./mvnw clean install -DskipTests followed by the targeted dotcms-integration test. Done means the integration and full test suites pass, REST and authentication flows work, OSGi bundles and plugins load, and Docker validation shows no ASM or bytecode errors.