davsclaus opened a new pull request, #29415: URL: https://github.com/apache/camel/pull/29415
[CAMEL-26733](https://issues.apache.org/jira/browse/CAMEL-26733) The Camel directory (`~/.camel`) keeps the log of the previous run of each integration name: `<name>-previous.log` and `<name>-previous.json`, for `camel log --previous` (CAMEL-25832). `camel dirty --clean` leaves them on purpose, but nothing ever removed them. There is one pair for each name that ever ran: on a developer machine that was 179 pairs going back to October, most of the 20 MB there. **Changes** - `camel dirty --clean --previous` also cleans them, and says how many files of how many integrations. - `camel dirty`, without `--clean`, says how many integrations have a previous run kept, and how to clean them. - `camel dirty --clean` without `--previous` is unchanged: it prints nothing about them and leaves them. - A log named `${sys:pid}.log` is now an orphan file. A logging configuration of the CLI writes that file name when the `pid` system property is not set yet. No process writes it again, and `pidOf` could not place it. **Docs:** the troubleshooting section of the configuration page, the 4.24 upgrade-guide paragraph about the previous run (it said `camel dirty` does not count them), the generated `camel dirty` page and the command metadata. **Tests** - `DirtyTest`: - the report line about previous runs; - `--clean --previous` removes both files of two integrations; - the `${sys:pid}.log` orphan; - the existing test that `--clean` alone leaves previous runs still passes unchanged. - The help golden (`cli-help.txt`) is updated for the new option. - Local runs: `DirtyTest` 10, plus `CliHelpGoldenTest`, `CliParseGoldenTest` and `RunExportGoldenTest`, all passing. _Claude Code on behalf of Claus Ibsen_ -- 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]
