-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 11 build breaks because of cobertura-maven-plugin #77
Comments
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? |
+1 to remove |
It looks like Cobertura isn't Java 11 compatible, see cobertura/cobertura#381. So fixing cobertura-m-p to be Java 11 compatible isn't possible. |
Discussion on dev mailing list: https://groups.google.com/forum/#!topic/mojohaus-dev/8cspr6c9o7k 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. |
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: