oscerd commented on PR #1905: URL: https://github.com/apache/camel-spring-boot/pull/1905#issuecomment-5440574300
**`check-doc` is now green** — which was the point of this PR. Documentation validation passes with all six starters removed. It took three iterations to get there, and the first two are worth recording because the failure mode is misleading: 1. **ironmq only** — that xref cleared, then `digitalocean`, `irc`, `json-patch` and `splunk` appeared. 2. **+ those four** — they cleared, then `langchain4j-tools` appeared. The published `next` docs catch up one component at a time, so a green run only proves nothing has propagated *yet*. Rather than keep reacting, every component xref under `docs/` was cross-checked against the 411 component pages that actually exist on camel `main`: ``` checked 377 xref targets, missing 0 ``` That is the basis for believing this set is complete, rather than just currently quiet. **The `build` job failure is not from this PR.** It is 630 occurrences of `Cannot run program "./mvnw"` in `camel-itest-spring-boot` archetype tests — no compilation errors, no dependency resolution failures. It hits any PR touching `tests/`, and every component removal deletes an integration test. #1902 failed identically and was merged. Two things deliberately **not** removed, since those components are still present in camel core: - `camel-splunk-hec-starter` — only `camel-splunk` was removed upstream - the six sibling `camel-langchain4j-*-starter` modules — only `camel-langchain4j-tools` was removed -- 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]
