oscerd opened a new pull request, #23140: URL: https://github.com/apache/camel/pull/23140
## Summary Stops re-embedding the full `pomContent` argument inside the `migrate_project` prompt instructions. Previously, `PromptDefinitions.migrateProject` inlined the entire pom.xml inside a multi-paragraph workflow block, so the prompt size grew linearly with pom size — duplicating content the client typically already has in conversation context. Verbose "Step 1 … Step 6" descriptions are also compressed into a tight numbered list. JIRA: [CAMEL-23477](https://issues.apache.org/jira/browse/CAMEL-23477) ## Changes - `pomContent` is now `required = false` (backward compatible — old clients still send it). - The prompt no longer interpolates the full pom content; instead it emits a one-line acknowledgement of whether a pom was supplied or should be read from conversation context. - Workflow descriptions compressed from ~6 paragraphs of "Step N: …" into a 6-item numbered list, preserving every tool call and decision branch (`camel_migration_analyze`, `camel_version_list`, `camel_migration_wildfly_karaf`, `camel_migration_compatibility`, `camel_migration_recipes`, `camel_migration_guide_search`). ## Test plan - [x] Updated `PromptDefinitionsTest`: - Replaced `migrateProjectContainsPomContent` (which asserted the pom was inlined). - Added `migrateProjectDoesNotInlinePomContent` — supplies a 1000×`<dependency/>` pom and asserts the resulting prompt size matches the size produced by a small pom, and that the large pom text is not present in the output. - Added `migrateProjectAcknowledgesSuppliedPom`, `migrateProjectFallsBackToContextWhenPomOmitted`, and `migrateProjectBlankPomFallsBackToContext`. - [x] `mvn verify` in `dsl/camel-jbang/camel-jbang-mcp` — passes. - [x] Full reactor build (`mvn clean install -DskipTests`) — passes; no regen artifacts. ## Acceptance > Prompt size does not scale with `pomContent` length. Verified by `migrateProjectDoesNotInlinePomContent`. --- _Claude Code on behalf of Andrea Cosentino_ -- 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]
