Skip to content

CAMEL-23910: camel-jbang - Quarkus version is now resolved automatic#24427

Open
davsclaus wants to merge 2 commits into
mainfrom
q
Open

CAMEL-23910: camel-jbang - Quarkus version is now resolved automatic#24427
davsclaus wants to merge 2 commits into
mainfrom
q

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

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.

AI-assisted contributions

  • If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., Co-authored-by trailers) and the PR description identifies the AI tool used.

@davsclaus davsclaus requested a review from Croway July 4, 2026 17:50
@github-actions

github-actions Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

🌟 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.

@github-actions

github-actions Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs
  • dsl/camel-jbang/camel-jbang-main

🔬 Scalpel shadow comparison — Scalpel: 2 tested, 1 compile-only — current: 0 all tested

Maveniverse Scalpel detected 3 affected modules (current approach: 0).

⚠️ Modules only in Scalpel (3)
  • camel-jbang-main
  • coverage
  • docs

Skip-tests mode would test 2 modules (2 direct + 0 downstream), skip tests for 1 (generated code, meta-modules)

Modules Scalpel would test (2)
  • camel-jbang-main
  • docs
Modules with tests skipped (1)
  • coverage

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-jbang-main. 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 (3 modules)
  • Camel :: Coverage
  • Camel :: Docs
  • Camel :: JBang :: Main

⚙️ View full build and test results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant