davsclaus opened a new pull request, #113:
URL: https://github.com/apache/camel-jbang-examples/pull/113

   JIRA: https://issues.apache.org/jira/browse/CAMEL-25670 (Camel side: 
apache/camel#27847)
   
   With `camel run --source-dir` in dev mode, every file under the folder is 
watched. So a route that writes into a folder of the example, such as an inbox, 
an outbox or an archive, reloaded the routes on every write, endlessly; 
`connect/file-processing` reloaded every 2 seconds and processed the same files 
again each time. `camel.jbang.dataDir` (Camel 4.24, apache/camel#27847) leaves 
such folders out of the reload. This PR declares them in the six examples that 
write into their own folder:
   
   | Example | `camel.jbang.dataDir` |
   |---|---|
   | connect/file-processing | `samples,inbox,archive` |
   | fail-well/error-handling | `orders,parked` |
   | transform/csv-to-json | `inbox,outbox` |
   | connect-service/camel-1-tribute | `outbox` |
   | ai/docling-langchain4j-rag | `documents,output` |
   | security/pqc-secure-file-transfer | `input,encrypted,decrypted` |
   
   - **Other examples:** the other ones that use the file component only read 
their files (`noop=true`), and `showcase/smart-log-analyzer` stores its files 
in `/tmp`.
   - **Bundled copies:** the first three are bundled in camel, and 
apache/camel#27847 adds the same lines there, so a later sync changes nothing.
   - **Older Camel versions** ignore the property.
   
   One PR for the six examples instead of one each, as Claus asked, since it is 
the same two-line change everywhere.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
   


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