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

   # Description
   
   [CAMEL-25919](https://issues.apache.org/jira/browse/CAMEL-25919): 
`DefaultDumpRoutesStrategy.setOutput` kept the `outputFileName` of an earlier 
file-style `setOutput` when it was then given a directory. A later dump to the 
directory still wrote to the old file name.
   
   This applies the fix suggested on the JIRA by @jamesnetherton: `setOutput` 
with a directory now resets `outputFileName`, so the dump writes the usual 
per-resource files.
   
   Test: `DefaultDumpRoutesStrategyOutputTest`, based on the reproducer from 
the JIRA. It dumps to a file, then to a directory, and checks the directory 
does not contain the old file name. It fails without the fix and passes with 
it. The other `DefaultDumpRoutesStrategy*` tests pass too.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   This PR was prepared with the help of Claude (Anthropic), credited with a 
`Co-authored-by` trailer in the commit.


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