luigidemasi opened a new pull request, #187:
URL: https://github.com/apache/camel-kit/pull/187

   Main probes and recovery and migration guidance could invoke a globally 
installed Camel version while generated `run.sh` used the project version. 
Align the four executable examples with `jbang camel@apache/camel run 
--camel-version={project.camelVersion}` and retain that project-context token 
during installation for all eight agents. Keep validation Stage 3 as a 
reporting-only handoff. Also correct the probe route's step nesting, which a 
real startup rejected as `Unsupported field: steps`.
   
   Addresses the [guidance inconsistency reported in 
#110](https://github.com/apache/camel-kit/issues/110#issuecomment-6523880505). 
#110 remains open for selectable JBang/Launcher support.
   
   Validation:
   - 60 focused tests passed, including installed resources for all eight agent 
generators and parsing the shipped probe YAML.
   - Four deliberate command/version regressions were each caught by all eight 
generators; the original malformed probe YAML also failed the new parser check.
   - All four commands ran successfully on Camel 4.18.4 and 4.22.1 without a 
global `camel` executable, including paths with spaces and the no-XSLT case.
   - `./mvnw -B clean install` passed across all 13 modules on Java 21: 2236 
passed, 11 existing conditional skips, zero failures/errors.
   - `./mvnw -B -Psourcecheck validate` passed.
   
   Website impact: not required; this restores the current JBang workflow's 
documented behavior. The broader backend-support documentation remains tracked 
by #159.
   
   _AI-generated by Codex on behalf of @luigidemasi._
   


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