[MNG-8320] Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR

[dependabot]

JIRA issue: MNG-8320

Bumps jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR.

Commits

• b07ba3d [maven-release-plugin] prepare release 2.0.1.MR
• da37685 [maven-release-plugin] prepare release 2.0.0-RC2
• b565201 [maven-release-plugin] 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[gnodet]

@dependabot ignore this minor version

[dependabot]

OK, I won't notify you about version 2.0.x again, unless you re-open this PR.

[gnodet]

@dependabot recreate

[dependabot]

Looks like this PR is closed. If you re-open it I'll rebase it as long as no-one else has edited it (you can use @dependabot reopen if the branch has been deleted).

[gnodet]

@dependabot reopen

[cdouillard]

Hi @gnodet, is the aim of this version change to use the multi-release jar ?

From what I see in the tag notes (2.0.1.MR Service Release (jakarta.inject) ) :

This is an experimental release to allow users to choose between this format of a modularized api jar and the 2.0.1 release that has the module-info.class in the root of the jar as is the convention adopted for EE10. Unless there is user feedback that this format has sufficient advantages over the 2.0.1 release format, this is not a format we intend to support in the future.

Since Maven 4 requires Java 17, I don't think this version change is necessary.

Tags notes are avalaible here :

• 2.0.1 Service Release (jakarta.inject)
• 2.0.1.MR Service Release (jakarta.inject)

[gnodet]

Hi @gnodet, is the aim of this version change to use the multi-release jar ?

From what I see in the tag notes (2.0.1.MR Service Release (jakarta.inject) ) :

This is an experimental release to allow users to choose between this format of a modularized api jar and the 2.0.1 release that has the module-info.class in the root of the jar as is the convention adopted for EE10. Unless there is user feedback that this format has sufficient advantages over the 2.0.1 release format, this is not a format we intend to support in the future.

Since Maven 4 requires Java 17, I don't think this version change is necessary.

Tags notes are avalaible here :

• 2.0.1 Service Release (jakarta.inject)
• 2.0.1.MR Service Release (jakarta.inject)

You're absolutely right, I misread the release notes.