feat(dsl): camel jbang export jib

[squakez]

Added a Jib profile to enable the publishing of the container via Jib profile

NOTE: this is separate from the existing jib flags which may be used in kubernetes plugin (via jkube and others).

Closes CAMEL-23780

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[davsclaus]

Can we use the same jib replacholder as in the k8s

              <version>[=JibMavenPluginVersion]</version>

[squakez]

JibMavenPluginVersion

I don't think so. That variable is enabled when the jkube plugin is enabled. The goal of this PR is separate from the Jkube one as it wants to include the plugin regardless of the presence of other tools. The idea is that the user can launch a mvn jib:build OOTB and have the same experience with all the runtimes we support as explained also in the readme.md files of each export.

[davsclaus]

Yeah but we should not hardcode the version, so it does not go stale

[squakez]

Yeah but we should not hardcode the version, so it does not go stale

Ah, okey. Sure, I'll see how to make it a variable then. Thanks!

[github-actions]

🧪 CI tested the following changed modules:

• dsl/camel-jbang/camel-jbang-core

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• dsl/camel-jbang/camel-jbang-core: 1 test(s) disabled on GitHub Actions

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-jbang-core. The related integration tests in dsl/camel-jbang/camel-jbang-it are excluded from CI. Consider running them manually:

mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test

All tested modules (6 modules)

• Camel :: JBang :: Core
• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container

---

⚙️ View full build and test results