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

   Backport of #30047 to camel-4.18.x.
   
   Cherry-pick (`git cherry-pick -x`) of 99f67905c0be (CAMEL-26977: camel-file 
- idempotentEager applies with a custom process strategy, and its description 
names the idempotent read locks), on top of #30080 (the backport of #30006). 
`idempotentEager` is turned off only when an idempotent read lock really runs: 
with a custom `processStrategy` the `readLock` option is not used. The 
`idempotentEager` description names the idempotent read locks, in the component 
JSON, catalog and endpoint DSL of file, ftp, ftps, sftp, mina-sftp, smb and 
azure-files.
   
   Adjustments:
   - The hunks of `camel-4x-upgrade-guide-4_18.adoc` and 
`camel-4x-upgrade-guide-4_22.adoc` are left out (the latter is not on this 
branch): the upgrade guides are published from main, where #30047 added the 
4.22.3 and 4.18.6 notes.
   - The 14 generated JSON files (7 components and their catalog copies) 
conflicted: on this branch the next line, `idempotentKey`, has no 
`"supportSimpleExpression": true`. In each file only the `idempotentEager` line 
is changed, from the same old text as on main to the same new text. The 
camel-file build regenerates `file.json` with no change.
   - The `Co-authored-by` trailer of the main commit is not carried over. 
`GenericFileEndpoint`, `FileIdempotentReadLockIdempotentConsumerTest` and the 7 
endpoint DSL files apply unchanged.
   
   Tests, on camel-4.18.x with JDK 25 (`mvnd test -pl core/camel-core -am 
-Dtest='File*Idempotent*,File*ReadLock*'`): 49 run, 0 failures, 3 skipped. 
`FileIdempotentReadLockIdempotentConsumerTest`: 6 tests pass, with the two new 
`customProcessStrategyKeepsIdempotentEager` cases. The build leaves no 
uncommitted change (formatter, regenerated `file.json`).
   
   _Claude Code on behalf of Federico Mariani_
   


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