Third-Party Dependency Compatibility

Resolve third-party library compatibility issues that arise during the Neo to Cloud Foundry migration.

Purpose

When migrating from Neo (Java 8, Java EE) to CF (Java 25, Jakarta EE 10, HANA Cloud), many third-party libraries break due to:

• Java 25 module system — removed javax.xml.bind, javax.xml.ws, and other javax.* modules from the JDK
• javax → jakarta namespace — libraries compiled against javax.servlet, javax.ws.rs, etc. won't link against Jakarta EE 10
• Database changes — schema migration tools may not recognize HANA Cloud
• DI framework conflicts — listener ordering, JNDI assumptions, and initialization sequences break when the platform changes

This skill scans the project's dependencies, identifies known compatibility issues, and applies targeted fixes.

Note: The jakarta-java25-migration skill handles the core javax→jakarta migration and Java 25 language upgrade. This skill handles third-party library-specific issues that the core migration doesn't cover.

Detection