Bump org.openclover:clover-maven-plugin from 5.0.1 to 5.1.0.1

[dependabot]

Bumps org.openclover:clover-maven-plugin from 5.0.1 to 5.1.0.1.

Changelog

Sourced from org.openclover:clover-maven-plugin's changelog.

[5.1.0.1] - 2026-07-29

Changed

• OC-323: When <jdk> is not defined, the source level now falls back to the <release> (maven.compiler.release) and <source> (maven.compiler.source) properties before falling back to auto-detection (based on runtime JVM).

[5.1.0] - 2026-07-26

Changed

• OC-309: Maven 4 compatibility. The clover:setup goal is now the recommended (and, on Maven 4, the only) way to instrument sources - it runs in the main lifecycle and does not mutate the project model.
• OC-309: maven.clover.repositoryPollutionProtection now defaults to true (it used to be false). Running the install or deploy phase while instrumentation is active fails the build. Set the flag to false to restore the previous behaviour.

Fixed

• OC-30: Improved handling of instrumented module dependencies. Prior to the fix, a dependency on a module of the same build was resolved to a -clover artifact from the local repository, which could come from some earlier build and not match current sources. Such a dependency now uses instrumented classes produced by that module in the current build - both a plain jar dependency (main classes) and a test-jar dependency (test classes) are resolved from the reactor.
• OC-309: The repository pollution protection never actually ran. AbstractCloverInstrumentMojo and CloverInstrumentInternalMojo both declared a mavenSession parameter, so the subclass field shadowed the superclass one and the latter stayed null - the build lifecycle analysis always failed with "Failed to call Maven's internals via reflections" and the protection was silently skipped. The duplicate declaration is gone and the underlying exception is now logged with the warning.

Deprecated

• OC-309: The clover:instrument and clover:instrument-test goals fail on Maven 4. They fork a build lifecycle and mutate the project model at runtime; Maven 4 treats the project model as immutable at execution time, so these mutations are not visible to the plugins running in the forked lifecycle. Both goals keep working on Maven 3.

[5.0.0] - 2026-07-16

Changed

• OC-194: Renamed the plugin package com.atlassian.maven.plugin.clover to org.openclover.maven.plugin, updated imported classes for OpenClover core 4.6.0+, and renamed packages in the code samples. Bumped OpenClover core to 5.0.0.
• OC-236: Raised the minimum required Maven version to 3.3.1 and updated the org.apache.maven dependencies and build plugin versions.
• OC-234: Dropped Java 1.7 support; source/target level raised from 1.7 to 1.8.
• OC-194: Migrated deployments to the ossrh-staging-api. Updated Groovy in the test cases to 4.0.32 (with matching groovy-eclipse batch/compiler).

Removed

• OC-194: Removed the gmaven-plugin and gmaven-plugin-no-java integration tests (the plugin has been dead for 14 years).

... (truncated)

Commits

• 336a3d1 Prepare release openclover-5.1.0.1
• 2cd7acb NONE: make possible to set Clover Core and Clover Maven Plugin versions indep...
• b06c35f Prepare for next development iteration
• c7fbefd Prepare release openclover-5.1.0.1
• 1f595c3 OC-323: use released Clover Core 5.1.0 instead of the snapshot
• 9324105 OC-323: Add fallback in clover-maven-plugin to <release> (maven.compiler.rele...
• f473cd5 Prepare for next development iteration
• a045229 Prepare release openclover-5.1.0
• 232df73 OC-322: use 1.8 source level
• c0c448a OC-322: bump clover core to 5.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)