> In our case, it is clear that the issue seems to come from
jacoco/emma conflict. Since I disabled Jacoco, a lot of things are back to work, and the
test Denis made on JSF that disabled emma and kept jacoco was fine too.
> So we don't hit the issue as described on the ticket, and only have trouble with
jacoco/emma conflict.
Yes I know - but we are now trying to fix the problem in jacoco on this.
Could we reproduce the issue and find the specific class that causes the problem and
attach it ?
No need for now - I went back and found the version of JBoss (7.0.2) that had same/similar
problem.
I've attached that file and we'll see if that helps them making jacoco more
resilient.
/max