Skip to content

The Jakarta Validation migration updates javax.validation:validation-api coordinate strings - #1272

Merged
jkschneider merged 1 commit into
jakarta/reflective-type-namesfrom
jakarta/validation-coordinate-literal
Oct 3, 2026
Merged

jkschneider merged 1 commit into
jakarta/reflective-type-namesfrom
jakarta/validation-coordinate-literal

Conversation

@jkschneider

Copy link
Copy Markdown
Member

Code that resolves an artifact by its coordinates, such as ShrinkWrap's Maven.resolver().loadPomFromFile("pom.xml").resolve("javax.validation:validation-api"), kept asking for the old artifact after the POM moved to jakarta.validation:jakarta.validation-api, so the version the POM manages no longer applied and resolution failed. JavaxValidationMigrationToJakartaValidation now replaces string literals equal to exactly javax.validation:validation-api with jakarta.validation:jakarta.validation-api using ReplaceStringLiteralValue. Literals that carry a version or any other text are left alone.

Found by a team of coding agents reviewing a Moderne run of org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta over the 31 Arquillian repositories (run 20261003120559-YQoma). The issue is maven-coordinate-literal-retained in the run's io.moderne.RecipeIssues data table (1 row), and the fix was discussed and reviewed on the run's message board. A row from the table, as a generalized example:

The migrated POM no longer manages the javax validation coordinates still requested by deployment code. (arquillian/arquillian-extension-spring, arquillian-warp-spring-ftest/src/test/java/org/jboss/as/quickstarts/spring/controller/Deployments.java, recipe org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta)

Before:

resolve("javax.validation:validation-api"); // POM manages javax.validation:validation-api

What the recipe produced:

resolve("javax.validation:validation-api"); // POM manages jakarta.validation:jakarta.validation-api

Expected:

resolve("jakarta.validation:jakarta.validation-api"); // POM manages jakarta.validation:jakarta.validation-api

Stacked on #1271 (9 of 19); merge that one first.

@jkschneider
jkschneider force-pushed the jakarta/validation-coordinate-literal branch from b06ddfb to 97c8515 Compare October 3, 2026 22:26
@jkschneider
jkschneider added this pull request to stack #1283 October 3, 2026 22:39
@jkschneider
jkschneider merged commit dc19e11 into jakarta/reflective-type-names Oct 3, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in OpenRewrite Oct 3, 2026
@jkschneider
jkschneider deleted the jakarta/validation-coordinate-literal branch October 3, 2026 22:41
jkschneider added a commit that referenced this pull request Oct 4, 2026
#1271)

* javax-reflective-names-retained: migrate runtime Jakarta type names

* maven-coordinate-literal-retained: migrate validation artifact lookups (#1272)

* weld-javax-provider-retained: align Weld core with Jakarta CDI (#1273)

* `JettyUpgradeEE9` also upgrades the other Jetty dependencies, the servlet packages and the Java version (#1274)

* jetty-ee9-java-baseline: align Jetty dependencies packages and Java baseline

* jetty-ee9-java-baseline: leave standalone Jetty utility dependencies unchanged

* jetty-ee9-java-baseline: require a direct dependency before upgrading Java

* `JacksonJavaxToJakarta` keeps newer Jackson versions and shared version properties when relocating artifacts (#1275)

* jackson-version-downgrade: preserve newer versions and shared properties

* jackson-shared-version-property-split: cover older shared Jackson versions

* The Jakarta JAXB migration keeps the `javax.xml.bind` API for Arquillian Recorder 1.x binaries (#1276)

* recorder-javax-jaxb-api-removed: retain the API needed by Recorder binaries

* recorder-javax-jaxb-api-removed: limit retention to external binaries after migration

* hibernate-validator-javax-provider-retained: migrate legacy validation providers (#1277)

* legacy-javaee-api-coordinate-retained: migrate legacy annotation EL and EJB aliases (#1278)

* The Jakarta migration keeps a provided API provided instead of adding it again in compile scope (#1279)

* cdi-provided-scope-promoted: preserve provided CDI API scope

* cdi-provided-scope-promoted: distinguish provided declarations from runtime APIs

* provided-api-scope-overwritten: preserve provided Mail API scope

* provided-api-scope-overwritten: preserve container API scopes across Jakarta migrations

* The Jackson Jakarta migration adds the `defaultView` parameter to `ProviderBase._configForWriting` overrides (#1280)

* jackson-provider-override-signature: forward the default view parameter

* jackson-provider-override-signature: update callers of migrated overrides

* invocation-context-get-constructor-missing: complete legacy decorators (#1281)

* jakarta-api-duplicates-platform: respect provided platform APIs (#1282)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant