Bump org.codehaus.plexus:plexus-build-api from 1.2.0 to 1.3.0

[dependabot]

Bumps org.codehaus.plexus:plexus-build-api from 1.2.0 to 1.3.0.

Release notes

Sourced from org.codehaus.plexus:plexus-build-api's releases.

1.3.0

[!CAUTION] Do not use 1.3.0. Two known regressions make it unusable:

• #127 — DefaultProgress carries both @Singleton and @MojoExecutionScoped, and 1.3.0 newly lists it in META-INF/sisu/javax.inject.Named. Guice rejects two scope annotations on one class, so the injector for any plugin realm holding this jar fails to build and Maven cannot load a single mojo from that plugin. Every goal fails, on Maven 3.9, 3.10, and 4.
• #125 — DefaultBuildContext gained a LegacySupport constructor dependency and can no longer be provisioned outside a Maven session.

Stay on 1.2.0 until 1.3.1 ships.

Three years of API work since 1.2.0. A Maven plugin can now report progress and messages through dedicated Progress and Messages APIs, execution events reach the environment running the build through an EventSpy rather than a lifecycle participant, and a connect API lets an IDE supply an extension to an external Maven process instead of watching it blind. The jar also declares Automatic-Module-Name.

• Delegate getValue/setValue in DefaultBuildContext to legacy build API (#108) @​Volodjam
• Create dedicated Messages API (#103) @copilot-swe-agent[bot]
• Remove obsolete TODO comments from BuildContext interface (#100) @copilot-swe-agent[bot]
• Add a Progress API (#98) @​laeubi
• Fix Artifact id returned instead of project version (#91) @​laeubi
• Add support for sending mojo execution events (#90) @​laeubi
• Use EventSpy to handle execution of events (#89) @​laeubi
• Add a connect API for inter-process-communication between maven and IDE (#88) @​laeubi

🚀 New features and improvements

• Establish an automatic module name (#121) @​slachiewicz

📝 Documentation updates

• Describe the artifact in the POM (#124) @​slachiewicz

🔧 Build

• Update parent to plexus 27 (#122) @​slachiewicz

📦 Dependency updates

• Bump plexus-utils to 4.1.0 (#123) @​slachiewicz
• Bump org.codehaus.plexus:plexus from 25 to 26 (#120) @dependabot[bot]
• Bump release-drafter/release-drafter from 7.6.0 to 7.7.0 (#119) @dependabot[bot]

... (truncated)

Commits

• ac42757 [maven-release-plugin] prepare release plexus-build-api-1.3.0
• 38638a4 Describe the artifact in the POM
• 81c80bd [maven-release-plugin] prepare for next development iteration
• 8233df9 [maven-release-plugin] prepare release plexus-build-api-1.3.0
• 6fb27d8 Bump plexus-utils to 4.1.0
• 1fa2d7d Update parent to plexus 27
• 6fb9b3e Establish an automatic module name
• df88871 Bump org.codehaus.plexus:plexus from 25 to 26
• 38cc7f3 Bump release-drafter/release-drafter from 7.6.0 to 7.7.0
• 9f502c4 Bump org.eclipse.sisu:org.eclipse.sisu.plexus from 1.0.1 to 1.1.0
• Additional commits viewable 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[slachiewicz]

Closing: plexus-build-api 1.3.0 should not be adopted. Two regressions in that release make it unusable, and this build hit the first of them.

• DefaultProgress carries two scope annotations, so 1.3.0 breaks every mojo in a plugin realm codehaus-plexus/plexus-build-api#127 — DefaultProgress carries both @Singleton and @MojoExecutionScoped, and 1.3.0 newly lists it in META-INF/sisu/javax.inject.Named. Guice rejects two scope annotations on one class, so the injector fails for any realm holding the jar.
• DefaultBuildContext cannot be provisioned outside a Maven session in 1.3.0 codehaus-plexus/plexus-build-api#125 — DefaultBuildContext gained a LegacySupport constructor dependency and can no longer be provisioned outside a Maven session.

What that looked like here, on ubuntu-latest jdk-17-zulu with Maven 3.10.0-rc-1:

com.google.inject.CreationException: Unable to create injector, see the following errors:

1) [Guice/DuplicateScopeAnnotations]: More than one scope annotation was found:
   Singleton and MojoExecutionScoped.
  at ClassRealm[plexus.core, parent: null]

EscapeStringTest 1 error, DefaultMavenResourcesFilteringTest 25 errors — the whole module.

Worth recording that this was the bump and not the environment: sibling Dependabot PRs #377 and #378 opened against the same branch minutes apart, and #378 passes the identical ubuntu-latest jdk-17-zulu 3.10.0-rc-1 cell that this one fails. Same base, same runner image, same hour.

Reopen or supersede this once a fixed release is out. Details from this occurrence are on codehaus-plexus/plexus-build-api#127.

This comment was created with AI assistance.