Bump jakarta.activation:jakarta.activation-api from 1.2.2 to 2.1.4

[dependabot]

Bumps jakarta.activation:jakarta.activation-api from 1.2.2 to 2.1.4.

Release notes

Sourced from jakarta.activation:jakarta.activation-api's releases.

Jakarta Activation 2.1.3 Final Release

The 2.1.3 release is a bug fix release of 2.1.x (Jakarta EE 10).

Following changes are included:

• fixes erroneous assumption about classes being loaded from Thread.getContextClassLoader
• allows reproducible build

Full Changelog: jakartaee/jaf-api@2.1.2...2.1.3

Jakarta Activation 2.1.2 Final Release

The 2.1.2 release is a bug fix release of 2.1.x (Jakarta EE 10).

Following changes are included:

• fix wrong class file version for package-info
• add missing javadoc description for MimeTypeEntry getters

Full Changelog: jakartaee/jaf-api@2.1.1...2.1.2

Jakarta Activation 2.1.1 Final Release

The 2.1.1 release is a bug fix release of 2.1.0.

Following changes are included:

• jakartaee/jaf-api#93 - Use OSGi service loader mediator
• jakartaee/jaf-api#94 - Loading of service provider implementations needs to be done under doPrivileged
• jakartaee/jaf-api#100 - Avoid requiring accessDeclaredMembers permissions

New Contributors

• @​yersan made their first contribution in jakartaee/jaf-api#95

Full Changelog: jakartaee/jaf-api@2.1.0...2.1.1

Jakarta Activation 2.1.0 Final Release

The 2.1.0 release provides API module only.

The implementation has been moved out from this project to the new Eclipse Angus project and lives in its own repository - https://github.com/eclipse-ee4j/angus-activation

Project Board: https://github.com/eclipse-ee4j/jaf/projects/1 Full Changelog: jakartaee/jaf-api@2.0.1...2.1.0

Jakarta Activation 2.0.1 Final Release

The 2.0.1 release is a bug fix release of 2.0.0.

Following changes are included:

• #53 - Android compilation failure due to possible badly formed compiler args in pom.xml
• #48 - Add version string to generated javadoc

Jakarta Activation 2.0.0 Final Release

... (truncated)

Commits

• 3dad341 Prepare release jakarta.activation:jakarta.activation-api:2.1.4
• 5f213b8 Rename resources so javax and jakarta can live in same classpath #174
• 510208a Merge pull request #155 from jakartaee/2.1.3-RELEASE
• e709bef Prepare next development cycle for 2.2.0-SNAPSHOT
• 7f7d358 Prepare release jakarta.activation:jakarta.activation-api:2.1.3
• 6126e90 update GH action build
• efc28c8 Use latest parent
• 4b8e7a1 allow reproducible build
• ce3e704 Jakarta Activation erroneously assumes that classes can be loaded from Thread...
• 80cb0f8 publish 2.1.2 release
• 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)

[holgerfriedrich]

@jbonofre I'd recommend to close this on the 4.4.x branch as 1.2.2 is the latest release of the 1.x series and we are not going to do the major version upgrade on that branch.

[jbonofre]

@holgerfriedrich agree, it makes total sense.

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