davsclaus opened a new pull request, #29341:
URL: https://github.com/apache/camel/pull/29341

   _Claude Code on behalf of Claus Ibsen_
   
   Quick fix, no JIRA.
   
   The `camel.jbang.dataDir` option has a `@Metadata` description written as 
string literals joined with `+` (in `CamelJBangConstants`). 
`PrepareCamelJBangMojo` read it with Roaster's `getStringValue`, which returns 
the source text of the concatenation. So the docs and the metadata got a `+` in 
the middle of the text:
   
   > Folders under the source directory (comma separated) that hold data the 
routes read or write, **+** not sources: in dev mode a change in them does not 
reload the routes. Use this for an **+** inbox, outbox or archive folder under 
the source directory.
   
   Main has this text since 84d4521a, and the CI regen check pushes it as a 
`Regen` commit into PRs that touch camel-jbang (for example #29338).
   
   ### Fix
   - `PrepareCamelJBangMojo.stringValue` reads the attribute's literal source. 
When it is string literals joined with `+`, it joins the literals (with their 
Java escapes). A single literal is read as before.
   - Regenerated: `camel-jbang-configuration-metadata.json` (camel-jbang-core 
and the catalog copy) and `camel-jbang-configuration.adoc`. Only the `dataDir` 
line changes.
   
   ### Tests
   - New `PrepareCamelJBangMojoTest`: a description joined from two literals is 
one text, and a single literal with a `+` and escaped quotes inside is 
unchanged.
   - `PrepareCamelJBangCommandsMojoTest` passes.
   - The generated files come from running the fixed plugin over 
camel-jbang-core. Both were installed into a scratch local repo, not `~/.m2`.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_012nJsFsjqqFiwroeHRWaKbS
   


-- 
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]

Reply via email to