davsclaus opened a new pull request, #30325: URL: https://github.com/apache/camel/pull/30325
[CAMEL-27153](https://issues.apache.org/jira/browse/CAMEL-27153) ## Problem The validator and the write tools of the camel-jbang-mcp server report a `direct:` or `seda:` endpoint that a route sends to and no route consumes (CAMEL-24955). After a write, the note says that the consuming route is not there yet, and to add it in the same `camel_edit_file` call. The check says nothing when the folder is a part of a Maven or Gradle project, as `src/main/resources/camel` is: the RouteBuilders under `src/main/java` are not in the folder. But a folder counted as a part of a project when *any* parent folder had a `pom.xml` or a `build.gradle`. So the check also said nothing in a folder that `camel run` runs on its own, such as an example in a repository with a `pom.xml` at its root. The local-model benchmark runs its examples in such folders, so the note never came up there. In route-enrich-and-dedupe step 3 (r35), the model added a `wireTap` to `direct:audit`, and the route from `direct:audit` only in a later write. In between, every order failed with `No consumers available on endpoint: direct://audit`. ## Change A folder is a part of a project only when it is under the `src` folder of the nearest parent project. A folder elsewhere in that project is checked. A project root, and `src/main/resources/camel`, work as before. ## Tests - `SourceValidatorEndpointConsumersTest`: a folder outside the sources of a project with a `pom.xml` is checked, and `src/main/resources/camel` of a module stays a part of the module. The new test fails without the change. - The write of r35 (route-enrich-and-dedupe step 3), checked in the benchmark's folder: the note now comes up. - camel-jbang-core, the `commands.ai` tests: 1094 run, 0 failures, 1 skipped. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016Y4dDi5iQNgtHrDdz2NpwF -- 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]
