davsclaus opened a new pull request, #28746: URL: https://github.com/apache/camel/pull/28746
_Claude Code on behalf of davsclaus_ Part of [CAMEL-24724](https://issues.apache.org/jira/browse/CAMEL-24724), after stage 2 ([CAMEL-24726](https://issues.apache.org/jira/browse/CAMEL-24726), #28739, #28740, #28741, #28743). camel-jbang-export is the engine of both `camel run` and `camel export` now, and a Java API for tools such as Kaoto: a run is an export with a run on top. As agreed when stage 2 started, the module is renamed after it, to camel-jbang-run, with its packages. 4.24 is not released yet, so this is the time; no code outside Camel uses these classes, so there are no shims and no upgrade-guide entry. ## Changes - **The module**: `dsl/camel-jbang/camel-jbang-export` is `dsl/camel-jbang/camel-jbang-run` (moved with `git mv`), artifactId `camel-jbang-run`, name `Camel :: JBang :: Run`. - **The packages**, so that the API of the runner is at the top (a literal rename would have given `org.apache.camel.dsl.jbang.run.run`): | Before | After | | --- | --- | | `org.apache.camel.dsl.jbang.export` (`ProjectExporter`, `ExportRequest`, `ExportContext`, `DependencyResolver`, the exporters) | `org.apache.camel.dsl.jbang.run.export` | | `org.apache.camel.dsl.jbang.export.run` (`ProjectRunner`, `RunRequest`, `RunContext`, `RunningIntegration`, `ConfiguredRun`, `RunPipeline`, the runners) | `org.apache.camel.dsl.jbang.run` | | `org.apache.camel.dsl.jbang.export.common` | `org.apache.camel.dsl.jbang.run.common` | | `org.apache.camel.dsl.jbang.export.catalog` | `org.apache.camel.dsl.jbang.run.catalog` | The classes of a package stay together, so nothing package-private changes. - **References**: the imports and the qualified names in the whole repository, the generated command metadata of camel-jbang-core and of the generate, Kubernetes and validate plugins, `dsl/camel-jbang/pom.xml`, `parent/pom.xml`, `bom/camel-bom/pom.xml`, `coverage/pom.xml`, the poms that depend on the module, the native workflows (`camel-launcher-native-exe.yml`, `package-native-validation.yml`), and "Exporting from Java" in the docs. - **camel-package-maven-plugin**: `PrepareCamelJBangMojo` reads the configuration constants (`CamelJBangConstants`) from the new path. camel-jbang-core sets that path explicitly (`configurationDir`) as well, for the builds that take the plugin from the Apache snapshots, which still have the old path until a new snapshot is published; that setting can be removed then. - What keeps the old name on purpose: the page of the `camel export` command (`jbang-commands/camel-jbang-export.adoc`), the `camel.jbang.export*` properties, and the classpath directory `export/` of the module's resources. No behaviour changes. ## Tests - `RunExportGoldenTest`: no change to the expected files (45 tests). - camel-jbang-run: 230 tests pass. - camel-jbang-core: 2422 tests in the default fork and 287 in the serial fork. The only failures, `EvalSimpleTest` (it runs the Camel installed with JBang) and 9 tests of the AI tools about the elvis operator of Simple, fail on `main` locally too. - The plugins (generate, Kubernetes, MCP, test, TUI, validate), camel-jbang-mcp and camel-jbang-it compile with their tests, the launcher compiles, and the `PrepareCamelJBang*` tests of camel-package-maven-plugin pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_0128ThHB3iQdrvSRLVBGRrdP -- 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]
