[
https://issues.apache.org/jira/browse/CAMEL-26733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-26733:
--------------------------------
Summary: camel-jbang - camel dirty --clean also cleans the logs of previous
runs (was: camel-jbang - camel dirty --previous: also clean the logs of
previous runs)
> camel-jbang - camel dirty --clean also cleans the logs of previous runs
> -----------------------------------------------------------------------
>
> Key: CAMEL-26733
> URL: https://issues.apache.org/jira/browse/CAMEL-26733
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> The Camel directory (~/.camel) keeps the log of the previous run of each
> integration name (<name>-previous.log and <name>-previous.json, CAMEL-25832,
> for camel log --previous). They are kept on purpose, so camel dirty --clean
> leaves them, but nothing ever removes them: one pair for each name ever run
> (179 pairs, most of 20 MB, on a developer machine).
> Add --previous to camel dirty: camel dirty says how many logs of previous
> runs there are, and camel dirty --clean --previous removes them too. Also
> clean a log named ${sys:pid}.log, which a log4j configuration writes when the
> pid property is not set.
> _Filed with Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
