Implement Kover Maven plugin

[binkley]

Kover looks very exciting! Thank you for the Gradle plugin.

Request: an equivalent Maven plugin. Projects I work on are around 50/50 Gradle/Maven for builds (these are for backend, not mobile).

[IgorSidorov]

+1
working with server side banking project.
Look forward to the maven equivalent.

[shanshin]

Hi,
at the moment, the development of the Maven plugin is not included in the short-term plans.

We will be happy to listen to your use cases, it will help to develop an API for the Maven plugin.

[KyongSik-Yoon]

+1
working with server side apm project.
Look forward to the maven equivalent

[marcoebbinghaus]

+1

Building maven based kotlin backend (REST API) application. I would like maven to create reports with kover during my CI.

[RustamKuramshin]

+1

[Filipe3xF]

+1

[prajain12]

+1 Very much interested in Kover Maven Plugin. JaCoCo still does not fully serve the purpose. For example JaCoCo does not exclude getters and setters from the code coverage of data classes.

[revseev]

+1
Server-side enterprise development

[Guruth]

+1
Server-side enterprise development

[khekrn]

+1
Server Side enterprise dev

[binkley]

A big reason I'm looking at Kover rather than JaCoCo is inline function coverage. See jacoco/jacoco#654.

@shanshin As to "use cases", I assume you mean why Maven? I don't want to have a religious debate of Gradle vs Maven ;-) I'm a consultant, and make recommendations to client teams and organizations on tech choices. For me, I often (but not always) prefer Maven, especially for certain types of client, because of stability and reproducibility of builds. And I encourage them to move to Kotlin from Java when feasible, and coach developer teams in that transition.

Here is a sample personal project with 100% coverage according to JaCoCo of lines, branches, and instructions: https://github.com/binkley/kunits. It builds with Maven. There are extension functions I'd like to mark as inline but at the cost of JaCoCo calling those lines uncovered.

[BerMuc]

+1

[stylismo]

+1

[ArtSaidanov]

+1

[valeria-luchko-idf]

+1

[Bernardoklopf]

+1

[raissa-machado]

+1

[NoxFr]

• 1!

[JulI0-concerto]

+1

[joao-soares-amaro]

+1

[oldratlee]

+1

from issue:

• Kotlin inline functions are not marked as covered jacoco/jacoco#654

[qwwdfsad]

Our long-term plan is the following: polish and stabilize Gradle API (so it's complete, future-proof and supports both Android and merged reports in a concise manner). As soon as it's done, released and evaluated, we'll start transferring this API shape into Maven plugin (which, alas, will be much less configurable and probably won't support merged reports as well).

No specific timeframes for this tho, it's just an outline of our overall direction

[pacdouglas]

+1

[SNandecha1]

+1

[hiteshgrover06]

+1

[acbeljaars]

+1

[emrearslan]

+1

[aloisgeith]

+1

[simon-void]

+1

[oldratlee]

+1

[kolesar-andras]

+1

[shanshin]

Implemented in 0.8.3