[
http://jira.codehaus.org/browse/MCLOVER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101940
]
John Allen commented on MCLOVER-72:
-----------------------------------
I think everyone would like to ditch the forked lifecycle, for lots of reasons
too, in fact I wish there was a suitable replacement that simply performed
bytecode based instrumentation with IDE integration but I don't know of one.
> Configurable to have inline lifecycle aswell as forked lifecycle
> ----------------------------------------------------------------
>
> Key: MCLOVER-72
> URL: http://jira.codehaus.org/browse/MCLOVER-72
> Project: Maven 2.x Clover Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Andrea Popplewell
>
> Request from a customer (TN#: 105209)
> Extract: it would be a big bonus with the 2.x maven plugin if it somehow did
> not require a forked lifecycle.
> It's so cumbersome to run the build twice that my team no longer does it, and
> we just allow coverage (and threshold checks) to happen on the server. I
> know the forked lifecycle is for safety's sake, more than anything else;
> Perhaps forking can be the default, but it becomes configurable to do inline
> as well. Then, devs can run inline, and the server can be run forked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
