oscerd opened a new pull request, #23934:
URL: https://github.com/apache/camel/pull/23934
## Problem
The docs `xref-check` goal currently fails on **every** `camel-4.18.x` PR
that regenerates docs, with two unresolved xrefs:
- `docs/user-manual/modules/ROOT/pages/camel-upgrade-recipes-tool.adoc` →
`xref:camel-jbang-projects.adoc#_automated_updates_openrewrite[...]`
- `dsl/camel-xml-io-dsl/src/main/docs/java-xml-io-dsl.adoc` →
`xref:manual:ROOT:camel-jbang-beans.adoc#_using_spring_beans_xml_in_camel_xml_dsl[...]`
## Cause
Commit `2d0c8fa35e7` ("Fix broken xref links after Camel CLI documentation
restructuring") was backported to `camel-4.18.x`. On `main` the Camel CLI
documentation was split (`camel-jbang.adoc` → `camel-jbang-projects.adoc`,
`camel-jbang-beans.adoc`, …) and that commit repointed the two xrefs to the new
split pages.
However, the CLI documentation **restructuring itself was not backported**
to `camel-4.18.x`, where `camel-jbang.adoc` is still a single page and the
split pages do not exist. So the backported xref "fix" points at pages that are
absent on this branch, breaking `xref-check`.
I verified: `camel-jbang-projects.adoc` and `camel-jbang-beans.adoc` are
**missing** on `camel-4.18.x` (present only on `main`), while
`camel-jbang.adoc` exists on `camel-4.18.x`.
## Fix
Revert `2d0c8fa35e7` on `camel-4.18.x`, restoring the xrefs to
`camel-jbang.adoc` with the anchors that exist on this branch (`#_update` and
`#_using_spring_beans_in_camel_xml_dsl` — both verified present in
`camel-jbang.adoc`). `xref-check` validates the target page, so pointing back
at the existing single page resolves both failures.
## Verification
Full `mvn clean install -Pregen -DskipTests` reactor build on `camel-4.18.x`
+ this change: `xref-check` reports **0 unresolved xrefs**, `BUILD SUCCESS`.
This unblocks docs regeneration for all open `camel-4.18.x` PRs.
---
_Claude Code on behalf of Andrea Cosentino_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
