Update dependency org.jacoco:jacoco-maven-plugin to v0.8.10 (release/4.0.x)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.jacoco:jacoco-maven-plugin (source)	0.8.8 -> 0.8.10

---

Release Notes

jacoco/jacoco (org.jacoco:jacoco-maven-plugin)

v0.8.10: 0.8.10

Compare Source

Fixed bugs

• Agent should not require configuration of permissions for SecurityManager outside of its codeBase (GitHub #​1425).

v0.8.9: 0.8.9

Compare Source

New Features

• JaCoCo now officially supports Java 19 and 20 (GitHub #​1371, #​1386).
• Experimental support for Java 21 class files (GitHub #​1386).
• Add parameter to include the current project in the report-aggregate Maven goal (GitHub #​1007).
• Component accessors generated by the Java compilers for records are filtered out during generation of report. Contributed by Tesla Zhang (GitHub #​1393).

Fixed bugs

• Agent should not open java.lang package to unnamed module of the application class loader (GitHub #​1334).

Non-functional Changes

• JaCoCo now depends on ASM 9.5 (GitHub #​1299, #​1368, #​1416).
• JaCoCo build now requires JDK 11 (GitHub #​1413).

---

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[zUniQueX]

JaCoCo previously added opens directives for java.lang which it doesn't do anymore (jacoco/jacoco#1334). Afterburner needs this declarations so we have to use a workaround here.

@dropwizard/committers Perspectively, I'd suggest to make the Afterburner dependency not only optional, but entirely remove it from the dropwizard-jackson module. Users could still declare it to have Afterburner registered instead of Blackbird, but this would solve the problem this workaround is needed for.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication