chore(deps): Bump mima-version from 2.4.48 to 3.0.1

[dependabot]

Bumps mima-version from 2.4.48 to 3.0.1.
Updates eu.maveniverse.maven.mima:context from 2.4.48 to 3.0.1

Release notes

Sourced from eu.maveniverse.maven.mima:context's releases.

3.0.1

MIMA 3.0.0 = Maven 3.10.0 + Resolver 2.0.24; same as 3.0.0

What's Changed

• Drop rogue dependency by @​cstamas in maveniverse/mima#288
• Updated Guava (used by Sisu runtime as transitive of Guice)

Full Changelog: maveniverse/mima@release-3.0.0...release-3.0.1

3.0.0

A lot!

MIMA 3.0.0 = Maven 3.10.0 + Resolver 2.0.24

Also provided new standalone-static-uber-url uber-jar usable for "consume only" use cases, where maven-resolver-transport-url transport is sufficient. New uber JAR is 2.3MB vs 4.2MB of "standalone-static-uber".

Code using MIMA 3.0.0 may be Maven 3.9.x compatible, as long no new method is touched. This is why "embedded-maven" runtime and "mmr" extension intentionally uses deprecated methods. As long user (your) code is not using Resolver 2.x features or APIs, you can support Resolver 1.x and Resolver 2.x.

What's Changed

• Parent POM 62 by @​cstamas in maveniverse/mima#279
• Bump org.apache.maven:apache-maven from 3.9.15 to 3.9.16 by @​dependabot[bot] in maveniverse/mima#280
• Bump com.google.guava:guava from 33.6.0-jre to 33.7.1-jre by @​dependabot[bot] in maveniverse/mima#282
• Bump org.mockito:mockito-core from 5.23.0 to 5.24.0 by @​dependabot[bot] in maveniverse/mima#283
• Parent POM 63 by @​cstamas in maveniverse/mima#285
• Maven 3.10 + Resolver 2.0 by @​cstamas in maveniverse/mima#270

Full Changelog: maveniverse/mima@release-2.4.48...release-3.0.0

3.0.0-alpha-3

Forward ported CLI improvements done in 2.x line.

What's Changed

• Update parent, CI and more by @​cstamas in maveniverse/mima#76
• CLI improvements by @​cstamas in maveniverse/mima#75

Full Changelog: maveniverse/mima@release-3.0.0-alpha-2...release-3.0.0-alpha-3

3.0.0-alpha-2

Uses Maven 4.0.0-alpha-12 and Resolver 2.0.0-alpha-6.

What's Changed

• Expand the CI matrix by @​cstamas in maveniverse/mima#69
• Use stdout / stderr + coloring for CLI output by @​cstamas in maveniverse/mima#68
• Improve exists command: accept artifact list by @​cstamas in maveniverse/mima#70

Full Changelog: maveniverse/mima@release-3.0.0-alpha-1...release-3.0.0-alpha-2

... (truncated)

Commits

• d2885d9 [maven-release-plugin] prepare release release-3.0.1 [skip ci]
• 186990d Update guava
• 95b364b Drop rogue dependency (#288)
• 5029a61 Adjust demo
• 4d9cb20 [maven-release-plugin] prepare for next development iteration
• 5d4c66f [maven-release-plugin] prepare release release-3.0.0 [skip ci]
• 5c991d3 Maven 3.10 + Resolver 2.0 (#270)
• 48bafda Parent POM 63 (#285)
• 5a8145a Bump org.mockito:mockito-core from 5.23.0 to 5.24.0 (#283)
• 4b107a2 Bump com.google.guava:guava from 33.6.0-jre to 33.7.1-jre (#282)
• Additional commits viewable in compare view

Updates eu.maveniverse.maven.mima.runtime:embedded-maven from 2.4.48 to 3.0.1

Updates eu.maveniverse.maven.mima.runtime:standalone-static from 2.4.48 to 3.0.1

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.

[apupier]

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.16.0:compile (default-compile) on project camel-tooling-maven: Compilation failure
Error: [ERROR] /home/runner/work/camel/camel/tooling/camel-tooling-maven/src/main/java/org/apache/camel/tooling/maven/MavenDownloaderImpl.java:[335,67] cannot find symbol
[ERROR]   symbol:   variable SnapshotUpdatePolicy
[ERROR]   location: class eu.maveniverse.maven.mima.context.ContextOverrides

[oscerd]

Not a safe bump as-is — mima 3.0.1 is a major that drops an API camel-tooling-maven relies on.

The build (17) / build (25) failures are a real compile break, not CI noise:

[ERROR] .../tooling/camel-tooling-maven/src/main/java/org/apache/camel/tooling/maven/MavenDownloaderImpl.java:[335,67] cannot find symbol
  symbol:   variable SnapshotUpdatePolicy
  location: class eu.maveniverse.maven.mima.context.ContextOverrides

ContextOverrides.SnapshotUpdatePolicy was removed/relocated in mima 3.x, so MavenDownloaderImpl no longer compiles and the -Pregen reactor fails at camel-tooling-maven. A version-only bump can't land here — it needs camel-tooling-maven migrated to the 3.x ContextOverrides API (whatever now controls the snapshot update policy in place of that constant).

Holding until that adaptation is made; this shouldn't be merged as a bare version change. (The Dependency Analysis non-blocking check is a separate, unrelated signal.)

This review was generated with AI assistance and reviewed/issued by the human operator. Claude Code on behalf of oscerd