Skip to content

Update clover.version to v5 - autoclosed - #1837

Closed
renovate-bot wants to merge 1 commit into
xwiki:masterfrom
renovate-bot:renovate/major-5-clover.version
Closed

Update clover.version to v5 - autoclosed#1837
renovate-bot wants to merge 1 commit into
xwiki:masterfrom
renovate-bot:renovate/major-5-clover.version

Conversation

@renovate-bot

@renovate-bot renovate-bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.openclover:clover (source) 4.5.25.1.0 age adoption passing confidence
org.openclover:clover-maven-plugin (source) 4.5.25.1.0 age adoption passing confidence

Release Notes

openclover/clover (org.openclover:clover)

v5.0.1

  • Issue #​249: Constructors in test classes were instrumented as test methods, producing uncompilable code.

v5.0.0

Added
  • Production-ready support for Java 17 with full instrumentation capabilities.
  • Runtime verification for Java 21 and Java 25.
  • Groovy: added support for Groovy 3.x through 5.x.
  • Groovy: instrumentation of lambda functions and method references in functional chains.
  • Groovy: synthetic default branch instrumentation for switch statements.
  • IntelliJ IDEA plugin support for versions 2024.2 through 2026.1.
  • Eclipse plugin support for versions 2024-06 through 2026-03.
Changed
  • Package namespace refactoring: all com.atlassian.* references replaced with org.openclover.*.
  • Maven minimum version requirement increased to 3.3.1.
  • Groovy: helper method visibility changed from private to package-private.
  • Use maven-shade-plugin to reduce JAR size.
Fixed
  • Over 40 issues resolved, including fixes for pattern matching, generic records, text blocks, switch statements, and try-with-resources parsing.
Removed
  • Deprecated Java 1.7 support; it is now treated as Java 8 with warnings.
  • Drop support for Groovy 2.x.
  • Remove Gson dependency.
openclover/clover-maven-plugin (org.openclover:clover-maven-plugin)

v5.1.0

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.

v5.0.0

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).
Fixed
  • OC-236: Removed usage of Strings.nullToEmpty, which caused a
    NoClassDefFoundError because Guava is not on Maven's classpath.
  • OC-213: The site:site goal now generates the "Goals" section with the plugin
    documentation (added maven-plugin-report-plugin).
  • OC-229: Added a test plan with Java 21.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

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


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

This PR was generated by Mend Renovate. View the repository job log.

@forking-renovate forking-renovate Bot added the dependencies A dependency upgrade label Jul 16, 2026
@renovate-bot renovate-bot added the dependencies A dependency upgrade label Jul 16, 2026
@renovate-bot
renovate-bot force-pushed the renovate/major-5-clover.version branch from 57c67ce to 7ded6a7 Compare July 21, 2026 03:06
@renovate-bot
renovate-bot force-pushed the renovate/major-5-clover.version branch from 7ded6a7 to e512d07 Compare July 26, 2026 13:46
@renovate-bot renovate-bot changed the title Update clover.version to v5 Update clover.version to v5 - autoclosed Jul 28, 2026
@renovate-bot
renovate-bot deleted the renovate/major-5-clover.version branch July 28, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies A dependency upgrade

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants