ammachado opened a new pull request, #23257: URL: https://github.com/apache/camel/pull/23257
# Description Fixes [CAMEL-23531](https://issues.apache.org/jira/browse/CAMEL-23531). The Jackson 2.x and 3.x dataformat lines share the same DSL `name` (`jackson`, `jacksonXml`, `avroJackson`, `protobufJackson`) so a runtime can drop in either variant transparently. The doc pipeline flattened both variants to the same destination filename, so the second symlink silently overwrote the first and only one entry appeared in the dataformats nav. Disambiguate at the doc layer only — runtime catalog and DSL behaviour are unchanged: - Rename the per-module `<name>-dataformat.adoc` source files with a `2` / `3` suffix in all eight Jackson modules. - Append the major-version suffix to the rendered `.adoc` title in `UpdateReadmeMojo` (driven by the artifactId), and look up the renamed page filename via the same suffix. The dataformat JSON `title` stays unsuffixed, so the catalog and `dataFormatJSonSchema` API keep their existing values. - Detect destination-basename collisions in `PrepareDocSymlinksMojo` and disambiguate Jackson-family `.json` symlinks via the same artifact rule. Any unresolvable collision now fails the build loudly instead of silently overwriting one source. - Regenerate the dataformats nav, page symlinks, JSON example symlinks, and per-module readme headers; both variants now appear with distinct titles (e.g. `JSON Jackson 2` / `JSON Jackson 3`). - Document the page renames in the 4.21 upgrade guide. The rename only affects the upcoming 4.x docs site; published docs for prior versions are unchanged and continue to serve their existing URLs. Adding `:page-aliases:` on the 3.x pages so the unsuffixed legacy URLs keep redirecting on the 4.x site is being discussed as a follow-up. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run \`mvn clean install -DskipTests\` locally from root folder and I have committed all auto-generated changes. --- _Claude Opus 4.7 on behalf of Adriano Machado_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
