davsclaus opened a new pull request, #30035: URL: https://github.com/apache/camel/pull/30035
JIRA: [CAMEL-26931](https://issues.apache.org/jira/browse/CAMEL-26931), item 10 (part). All checked on the launcher built from main before the change. - **`camel transform route --format=java --output=Out.java`** wrote `public class Tick` into `Out.java`, a class named after the route file, which does not compile. The class is now named after the file it is written to; a directory output is unchanged. - **`camel doc split`** (any EIP) printed an empty `Since:` line, as the catalog has no first version for EIPs. The line is left out when there is no version, for all doc kinds. - **The help showed `<<file>>` and `<<files>>`.** aesh adds the brackets itself to a `paramLabel`, so the 18 labels now read `file` or `files`, in core, edit, kubernetes and validate. - **`camel plugin get`** without plugins printed nothing; it now says so on stderr and points to `camel plugin list`. **`camel infra ps`** with nothing running printed only the header of the table; it now says "No running infrastructure services" on stderr. `--json` is unchanged. - **`camel eval --help`** said "use transform --help to see sub commands". Tests: - new: `TransformRouteTest.yamlToAJavaFileNamesTheClassAfterTheFile`; - extended: `CatalogDocTest` (no empty Since for an EIP), `PluginGetTest`, `InfraPsTest`; - the golden help is updated. The core, edit, kubernetes and validate suites are green. `DependencyUpdateTest` failed once and passed on rerun; it fails once per run on every branch. Left of item 10: - `dependency update` newlines; - `camel wrapper` on a SNAPSHOT; - `catalog --filter` and `--sort`; - the required-argument error text; - the camelCase options of `camel update run`; - `camel bind` reading Kamelets from GitHub; - `--json` for the other commands listed; - an environment variable for the CLI home. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
