> On 04/03/2012 04:38 PM, Max Rydahl Andersen wrote:
>> btw. I've seen this exact error in other cases than emma/jacoco conflicts and
discussed it with Marc Hoffman before about possible fixes to this.
> That's very interesting.
> I'm trying to make some experiments locally to see if the issue may come from
jacoco by itself jacoco+bytecode, or if it is a tricky issue that is consequence of
Emma+Jacoco+bytecode.
No need to experiment more for JSF: tests are OK with jacoco only:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf...
(I think that's what Denis G tried) So it confirms we are not facing issue described
in
http://sourceforge.net/apps/trac/eclemma/ticket/196
huh? that shows to me we exactly hit that issue.
eclemma gets added into the mix and buildtime instrument the classes with some subtle
errors in it.
now jacoco gets affected - just like #196 says.
/max