I think the use of war:inplace should be removed. It's a nasty hack to
make jetty:run work with war overlays. I was planning to look at the
Jetty plugin as I think they have an option to add additional source
directories now that would mean this and all the obscure clean plugin
config could
It turns out the Emma plugin is also having the same problem with
war:inplace as Cobertura. I looked at the source code of Emma and it has the
same default lifecycle where the classesDirectory is being set, which is
causing the same error 'Cannot override read-only parameter:
classesDirectory in go
+1 too
Emmanuel
On Wed, Sep 23, 2009 at 8:20 AM, Brett Porter wrote:
> +1 for EMMA, since it works in Eclipse and IDEA as well.
>
>
> On 23/09/2009, at 4:03 PM, Deng Ching wrote:
>
> Hi All,
>>
>> I'll be configuring code coverage on Continuum trunk and 1.3.x branch to
>> identify which classe
+1 for EMMA, since it works in Eclipse and IDEA as well.
On 23/09/2009, at 4:03 PM, Deng Ching wrote:
Hi All,
I'll be configuring code coverage on Continuum trunk and 1.3.x
branch to
identify which classes still lack tests. I'm considering using
either the
Cobertura plugin or the Emma plug
Hi All,
I'll be configuring code coverage on Continuum trunk and 1.3.x branch to
identify which classes still lack tests. I'm considering using either the
Cobertura plugin or the Emma plugin. There is a problem with Cobertura and
war:inplace goal though as we encountered in Archiva (
http://jira.c
