Or we could simply remove the Cobertura plugin from the Mojo-Parent site, and include it for those plugins using Cobertura.
While I am uncertain about the state of the Cobertura running on Java8+ (and Java 11+ for that matter), it seems that the Mojo integrations with Cobertura requires quite a few complex twists within the POM - men to the point where it actually hampers progress. Could we remove it from the MojoHaus-Parent re-introduce Cobertura when it is actually updated for JDK 8+ or JDK 11+? Den tisdag 9 juli 2019 kl. 22:24:51 UTC+2 skrev Jochen Wiedmann: > > On Tue, Jul 9, 2019 at 7:44 PM Lennart Jörelid > <[email protected] <javascript:>> wrote: > > > > Actually, it does not. > > > > The problem is that the IT:s in mojo-parent version 50 are run with > Cobertura instrumentation. > > The implication of this is that the POM of each IT needs the Cobertura > depdendency within the plugin dependencies when running the mvn site goal. > > Would declaring the dependency as an extension help? See > > https://maven.apache.org/guides/mini/guide-using-extensions.html > > Jochen > -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/591a9b84-cf87-4e0b-9ef1-a75dca9f4850%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
