[
https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on WFLY-9406:
------------------------------------
I don't fully understand how the version of ASM that WildFly uses internally should
impact Jacoco. Can you add more details on what issues you are running into, including any
exception stacktraces? The whole point of a modular classloading is to avoid issues like
these and as far as I know, WildFly doesn't attach/expose the ASM module
(automatically) into the deployments.
[WildFly 11] Upgrade ASM with Version 5.2 (unable to use
Arquillian+JaCoCo with ASM 3.3.1)
------------------------------------------------------------------------------------------
Key: WFLY-9406
URL:
https://issues.jboss.org/browse/WFLY-9406
Project: WildFly
Issue Type: Component Upgrade
Components: CDI / Weld, Class Loading, REST
Affects Versions: 11.0.0.CR1
Reporter: Tibor Digana
Assignee: Martin Kouba
Priority: Critical
Fix For: 11.0.0.Final
Reported in GitHub
https://github.com/wildfly/wildfly/issues/10531
Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and
JaCoCo uses ASM 5.2.
The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class
{{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in
ASM 3.3.1.
Please upgrade it in POM:
https://github.com/wildfly/wildfly/blob/master/pom.xml
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)