You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project is not buildable with Java 11. It fails due to the cobertura-m-p, which can be seen in the Travis builds.
Also see #39 and #59 which are about issues with cobertura.
The issue about java 11 filed for cobertura-m-p: mojohaus/cobertura-maven-plugin#43
The text was updated successfully, but these errors were encountered:
As cobertura-m-p isn't Java 11 compatible, what should we do? Should we fix it, or should we switch to some other code coverage tool? If we should switch, to what?
Or, should we just remove the code coverage report all together? I think our mojos mainly have tests via the invoker-m-p so that coverage will not be included in the report anyways as those tests are not instrumented.
Conclusion: I nice thing to have, but need to switch to e.g. JaCoCo. Most likely we need to instrument the invoker-m-p driven tests as well as most mojo test are there.
But for now we settle on removing coberture-m-p. Something else could be added in the future if needed.
andham
added a commit
to andham/mojo-parent
that referenced
this issue
Jan 21, 2020
The project is not buildable with Java 11. It fails due to the cobertura-m-p, which can be seen in the Travis builds.
Also see #39 and #59 which are about issues with cobertura.
The issue about java 11 filed for cobertura-m-p: mojohaus/cobertura-maven-plugin#43
The text was updated successfully, but these errors were encountered: