[timtebeek]

Summary

• JettyUpgradeEE10 mapped three EE9 artifacts to EE10 coordinates that have no Jetty 12 release on Maven Central. Every project using them ended up with an unresolvable POM.
• Map them to the Jetty 12 core modules that do exist, and keep newVersion: 12.0.x.

Problem

EE9 artifact	Previous target	Published versions of the previous target
org.eclipse.jetty.ee9:jetty-ee9-security	org.eclipse.jetty.ee10:jetty-ee10-security	never published
org.eclipse.jetty.ee9.websocket:jetty-ee9-websocket-jetty-api	org.eclipse.jetty.ee10.websocket:jetty-ee10-websocket-jetty-api	12.0.0.alpha0..12.0.0.beta0 only
org.eclipse.jetty.ee9.websocket:jetty-ee9-websocket-jetty-client	org.eclipse.jetty.ee10.websocket:jetty-ee10-websocket-jetty-client	12.0.0.alpha0..12.0.0.beta2 only

Before this change, the new test produced:

• jetty-ee10-security failed. Unable to download metadata ... HTTP 404, with jetty-ee9-security left in place.
• Unable to download POM: ...jetty-ee10-websocket-jetty-api:12.0.x (and the same for -client). Both dependencies were rewritten with the literal 12.0.x, because no matching release exists.
• Error markers that kept accumulating, so the recipe never settled after one cycle.

Solution

• jetty-ee9-security → org.eclipse.jetty:jetty-security
• jetty-ee9-websocket-jetty-api → org.eclipse.jetty.websocket:jetty-websocket-jetty-api
• jetty-ee9-websocket-jetty-client → org.eclipse.jetty.websocket:jetty-websocket-jetty-client

These were found in a catalog-wide check of dependency-swap steps against Maven Central metadata.

Not addressed here: JettyUpgradeEE10 changes dependencies but not the matching org.eclipse.jetty.ee9.* → org.eclipse.jetty.ee10.* Java packages, apart from one ChangeType.

Test plan

• New JettyUpgradeEE10Test fails before the change and passes after
• JettyUpgradeEE9Test and JakartaEE10Test pass