Hi everyone, (This is related to the maven plugin).
Given a codebase where the current coverage is lower than a set goal, one has to deliberately set the limits too high when running the check goal in order to see the current coverage levels. The other option, of course, is to check out the generated reports and read the values off of them. With a multi module project, this could be somewhat tedious, and reporting the current coverage for each module directly in the maven outout could be useful. What do you say to for instance implementing a "verbose" flag to the check goal? As it happes, I've tried that out myself and could create a pull request with that functionality if you are interested. Regards, Håvard -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
