abashev commented on issue #63: Use codecov.io for calculating code coverage URL: https://github.com/apache/commons-vfs/pull/63#issuecomment-492208855 It looks like a little misunderstanding about my changes - there are two components work together on code coverage. One is an agent for gathering coverage data (JaCoCo or Cobertura) and another is external service to gather historical data (Codecov or Coverall). Cobertura is abandoned project, it doesn't support annotations and latest Java 8+ features. So I think we don't needto spend time on keeping this plugin inside pom. And JaCoCo is only one option that works fine with latest Java and has been supported by all code coverage services. I didn't put JaCoCo into <reporting> tag because I think single report doesn't make any sense and gives zero information about the project itself. Because from my understanding the only thing that matter for code coverage is changing of coverage. And here come external services that gather historical data - Codecov and Coverall. If you are submitting huge pile of code then only changing of code coverage could say you did you spend enough efforts on writing tests or not. There is how it looks like for vfs-s3 https://codecov.io/gh/abashev/vfs-s3/commits In first I wanted to keep Coverall and migrate vfs-s3 on it too. But it looks like coverall never worked for commons-vfs and you don't have any historical data about the coverage. Another issue is if you want to have coverall reports then need to add one more maven plugin into pom. In compare Codecov works directly with JaCoCo reports and don't need to update pom at all. And last but not least, Coverall looks neglected for me - latest tweet from 2017 https://twitter.com/CoverallsApp no any activity in issue tracker for months. And in compare Codecov is more active with more followers https://twitter.com/codecov?lang=en You are main contributor so that is up to you - I can move JaCoCo into <reporting> and fix coverall integration but you should have in mind that there is an alternative.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
