chore(deps): Bump org.eclipse.sisu:org.eclipse.sisu.inject from 1.0.1 to 1.1.0

[dependabot]

Bumps org.eclipse.sisu:org.eclipse.sisu.inject from 1.0.1 to 1.1.0.

Release notes

Sourced from org.eclipse.sisu:org.eclipse.sisu.inject's releases.

1.1.0

Eclipse Sisu 1.1.0 release. Added new feature: JSR330 bean filtering.

Important: when using Sisu Plexus Shim (that implicitly creates Sisu Inject), the JSR330 bean filtering will automatically "follow" (have same filtering rules applied) the Plexus Beans visibility. Control this behaviour using Plexus Container Configuration new method.

Users of Sisu Inject only (without Plexus Shim) are not affected by this change.

What's Changed

• Update Security Policy by @​cstamas in eclipse-sisu/sisu-project#264
• Build update by @​cstamas in eclipse-sisu/sisu-project#267
• Feat: Ability to filter JSR330 beans based on some predicate by @​cstamas in eclipse-sisu/sisu-project#266
• Update conversion doc by @​cstamas in eclipse-sisu/sisu-project#268
• Introduce more tests for lifecycle by @​cstamas in eclipse-sisu/sisu-project#269

Full Changelog: eclipse-sisu/sisu-project@releases/1.0.1...releases/1.1.0

Commits

• 202effd | prepare release releases/1.1.0
• cd2cd85 Introduce more tests for lifecycle (#269)
• f32a35e Update conversion doc (#268)
• 41467dd Feat: Ability to filter JSR330 beans based on some predicate (#266)
• e057b23 Build update (#267)
• a5ded53 Update Security Policy (#264)
• 1d2e69c | prepare for next development iteration
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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

[github-actions]

🧪 CI tested the following changed modules:

• dsl/camel-jbang/camel-launcher

---

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

Maveniverse Scalpel detected 2 affected modules (current approach: 1).

⚠️ Modules only in Scalpel (1)

• camel-launcher

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

Modules Scalpel would test (2)

• camel-launcher
• camel-launcher-container

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

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-launcher. 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 (2 modules)

• Camel :: Launcher
• Camel :: Launcher :: Container

---

⚙️ View full build and test results