Hi Erwan, all,
I agree with you that the underlying problem should be fixed. That's why we
have the issue registered in Jira.
Analogous to this issue and other that have patches, that are perceived as
hacks, is the waterpipe with a rip in it. While the bandaid doesn't fix the
underlying problem, it fixes temporarily the spillage of water.
In this case, the workaround (which has a better connotation than hack)
will enable us to do better testing and code coverage analysis and identify
other issues that can and need to be fixed in future releases. Specifically
when doing it with continiuous integration.
Moreover, when not implementing the workaround, we continuously send out
the message to our community that our product is broken. In every release
that is out there, but also our trunk. I don't think that that message is
good for the adoption and spread of the product.
The Jira is there to not forget the underlying issue, the fix is there to
help us do our work until someone steps up with the expertise and time
available to pick the issue up and solve it for good.
Regards,
Pierre
Op 6 april 2012 21:57 schreef Erwan de FERRIERES <
[hidden email]> het volgende:
> Le 06/04/2012 16:43, Pierre Smits a écrit :
>
> Hi all,
>>
>> Revision 1309337 has broken the possibility to do testing with cobertura
>> code coverage analysis.
>>
>> Please revert to r1308301 so that it works again.
>>
>> Regards,
>>
>> Pierre
>>
>> Hi Pierre,
>
> I reverted as it was considered as a hack. I created the correspondant
> jira issue, but I'm not able to correct the ./ant script. I hope that some
> will be able to take care of it quickly.
>
> Cheers,
>
> --
> Erwan de FERRIERES
> www.nereide.biz
>
Locked
