Skip to content

Conversation

timtebeek
Copy link
Member

While JaCoCo is a likely replacement, actually plugging that in would
likely also require integration with whatever the build was using to
visualize the results. It is unlikely there is a direct replacement
option there.

Removing Cobertura at least ensures the build is not left in a broken
state, even though Coverage information may then be missing. Any
coverage visualization is likely to surface that for users.

Tim te Beek added 2 commits April 25, 2022 21:06
While JaCoCo is a likely replacement, actually plugging that in would
likely also require integration with whatever the build was using to
visualize the results. It is unlikely there is a direct replacement
option there.

Removing Cobertura at least ensures the build is not left in a broken
state, even though Coverage information may then be missing. Any
coverage visualization is likely to surface that for users.
Copy link
Contributor

@tkvangorder tkvangorder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds reasonable to me, thanks for the contribution!

@tkvangorder tkvangorder merged commit 79cb372 into openrewrite:main Apr 26, 2022
@timtebeek timtebeek deleted the remove_cobertura branch April 26, 2022 07:31
@tkvangorder tkvangorder added the bug Something isn't working label Apr 28, 2022
@tkvangorder tkvangorder added this to the 1.5.0 milestone Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants