Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78283012
No, and I would not advocate the use of tools like that which would distort
the standard lifecycle and promote tools like Jacoco that do not require things
like that. As a tool that collaborates with the standard build lifecycle it
should be able to operate on either data emitted by the eventing system in
Maven or operate on, or use artifacts as they are produced from the system.
Like adding an agent to dynamically instrument code. Tools like Clover and
Cobertura are frankly terrible tools that are super hard to integrate and we've
done some stupid things in the core to accommodate them and that was
categorically a mistake. If things like Clover and Cobertura break in Maven 4.x
I honestly don't care. They are designed incorrectly in my opinion or were
designed for a time where there didn't exist proper support to be truly
independent from how Maven operates. The model should be "report on standard
data produced, or by looking at standard artifacts being produced", not I'm
going t
o "jam myself into the process to completely alter how the build works to get
the data I need."
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
