Are you now doing these checks as part of a normal "m2 install" build?
That is probably a bit heavier than I'd have thought it should be, but
probably a valid use case.
Previously, you had talked about running it as "m2 clover:clover" and
doing all of those checks in there.
Do you think you could have a go at designing how you think this will be
used, so we can compare it to the lifecycle design and propose
solutions? Some of this still needs to be implemented, which I'll be
working on this week.
Please enumerate all the use cases (including reports, as even if you
aren't doing it now it is important), how the user will configure it and
how the user will run it.
- Brett
Vincent Massol wrote:
Hi,
For the Clover plugin, I have a use case where the clover:check goal will
verify that the test coverage percentage is above a specific value. If not,
the build will fail. I need to bind this clover:check to a phase.
However I find none that suits this use case. The integration-test phase is
too early as IT can contribute test coverage data. The following phase is
install which is too late.
I think there's a need for a "verification" phase (or "post-test" or any
other name) that would be used to perform additional verifications like:
checkstyle checks, clover checks, pmd checks, simian checks, etc.
WDYT?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
