Remove jacoco from the managed set

[basil]

https://plugins.jenkins.io/jacoco/ is formally deprecated, so no need to manage this anymore. But first we probably need to remove its integration in the non-deprecated Pipeline Maven plugin.

[alecharp]

Jacoco plugin is an optional dependency on Pipeline Maven plugin (https://github.com/jenkinsci/pipeline-maven-plugin/blob/658737b64753e2834e5d79181531d9d5fe0276a8/pipeline-maven/pom.xml#L150). Is it essential to remove it?

EDIT: nevermind, I'm not sure the code would work properly without the plugin: https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/pipeline-maven/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JacocoReportPublisher.java

[basil]

Not sure offhand. If the BOM/PCT test suite passes with JaCoCo plugin removed, then I guess we would not need to touch Pipeline Maven plugin.

[jglick]

It may pass now, but then cause problems later when dependencies in jacoco and dependencies in pipeline-maven fall out of synch. (One of the original purposes of creating bom was to prevent this sort of misalignment.) OTOH if jacoco is rarely touched and only pipeline-maven is getting POM updates maybe this will not become an issue. Regardless, the integration in pipeline-maven ought to be removed I guess. (It could perhaps be moved to jacoco to minimize disruption for anyone still relying on jacoco.)

[basil]

Regardless, the integration in pipeline-maven ought to be removed I guess.

That does seem safest.

[alecharp]

the integration in pipeline-maven ought to be removed I guess.

I can work on that.

[alecharp]

See jenkinsci/pipeline-maven-plugin#881