[JBoss JIRA] (ARQ-1936) Jacoco Extension needs signature removal
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1936?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1936:
-------------------------------
Fix Version/s: jacoco_1.0.0.next
> Jacoco Extension needs signature removal
> ----------------------------------------
>
> Key: ARQ-1936
> URL: https://issues.jboss.org/browse/ARQ-1936
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Jacoco
> Environment: WildFly 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Fix For: jacoco_1.0.0.next
>
>
> Jacoco normally removes signatures using SignatureRemover. Because Arq Jacoco Extension is dealing with Archives and Assets it invokes instrumenter directly by hand. The normal process of signature removal doesn't happen and corrupted jars fail to be read with errors such as this.
> {noformat}
> 2015-03-21 07:49:08,062 WARN [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015852: Could not index class org/jacoco/core/internal/flow/ClassProbesAdapter.class at /content/27ab3865-48b4-48c0-b2b5-dbbfd128ed38.ear/lib/org.jacoco.core-0.7.4.201502262128.jar: java.lang.SecurityException: SHA-256 digest error for org/jacoco/core/internal/flow/ClassProbesAdapter.class
> at sun.security.util.ManifestEntryVerifier.verify(ManifestEntryVerifier.java:218) [rt.jar:1.8.0_40]
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:241) [rt.jar:1.8.0_40]
> at java.util.jar.JarVerifier.update(JarVerifier.java:228) [rt.jar:1.8.0_40]
> at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:482) [rt.jar:1.8.0_40]
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) [rt.jar:1.8.0_40]
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) [rt.jar:1.8.0_40]
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345) [rt.jar:1.8.0_40]
> at java.io.DataInputStream.readFully(DataInputStream.java:195) [rt.jar:1.8.0_40]
> at java.io.DataInputStream.readFully(DataInputStream.java:169) [rt.jar:1.8.0_40]
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433) [jandex-1.2.1.Final.jar:1.2.1.Final]
> at org.jboss.jandex.Indexer.index(Indexer.java:689) [jandex-1.2.1.Final.jar:1.2.1.Final]
> at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar
by Chris Rankin (JIRA)
[ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.s... ]
Chris Rankin updated ARQ-1944:
------------------------------
Attachment: arquillian-hamcrest-test.tar.xz
Simple example Maven project.
> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
> Key: ARQ-1944
> URL: https://issues.jboss.org/browse/ARQ-1944
> Project: Arquillian
> Issue Type: Bug
> Affects Versions: 1.1.7.Final, 1.1.8.Final
> Environment: JDK7, Windows 7 x64, Linux x64
> Reporter: Chris Rankin
> Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.50 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in three different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar
by Chris Rankin (JIRA)
Chris Rankin created ARQ-1944:
---------------------------------
Summary: Linkage error with arquillian-junit.jar
Key: ARQ-1944
URL: https://issues.jboss.org/browse/ARQ-1944
Project: Arquillian
Issue Type: Bug
Affects Versions: 1.1.8.Final, 1.1.7.Final
Environment: JDK7, Windows 7 x64, Linux x64
Reporter: Chris Rankin
Testing a WAR in embedded Tomcat >= 7.0.50 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
The test fails with this error message:
{code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR!
java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
{code}
This error can be resolved in three different ways:
- Rewrite the test using TestNG
- Rewrite the test without using any Hamcrest matchers.
- Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARQ-1943) Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when deployment contains bean archive
by Chris Rankin (JIRA)
[ https://issues.jboss.org/browse/ARQ-1943?page=com.atlassian.jira.plugin.s... ]
Chris Rankin updated ARQ-1943:
------------------------------
Attachment: arquillian-test.tar.xz
I've updated my sample project:
- Arquillian 1.1.8.Final
- WELD 2.2.10.SP1
- Removed the "suite" extenstion (seeing as there's only one test anyway).
This sample project demonstrates the same error as the original.
> Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when deployment contains bean archive
> --------------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1943
> URL: https://issues.jboss.org/browse/ARQ-1943
> Project: Arquillian
> Issue Type: Bug
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Environment: Windows 7 x64, Linux x64, JDK7
> Reporter: Chris Rankin
> Attachments: arquillian-test.tar.xz, arquillian-test.tar.xz
>
>
> Using arquillian-tomcat-embedded-7, arquillian-bom 1.1.7.Final, WELD 2.2.10.Final:
> I have created a simple WAR file that contains WELD and a single servlet. There is also a dependent JAR that contains the following:
> - a @Dependent bean with a @Produces method
> - a META-INF/beans.xml file.
> When I try to test this servlet using Arquillian's TestNG container, the deployment fails with this error:
> SEVERE: Servlet threw load() exception
> org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type String with qualifiers @Trouble
> at injection point [BackedAnnotatedField] @Trouble @Inject private org.testing.web.TroubleServlet.trouble
> at org.testing.web.TroubleServlet.trouble(TroubleServlet.java:0)
> Possible dependencies:
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()],
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARQ-1943) Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when deployment contains bean archive
by Chris Rankin (JIRA)
[ https://issues.jboss.org/browse/ARQ-1943?page=com.atlassian.jira.plugin.s... ]
Chris Rankin updated ARQ-1943:
------------------------------
Summary: Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when deployment contains bean archive (was: Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when beans inside a dependent JAR.)
> Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when deployment contains bean archive
> --------------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1943
> URL: https://issues.jboss.org/browse/ARQ-1943
> Project: Arquillian
> Issue Type: Bug
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Environment: Windows 7 x64, Linux x64, JDK7
> Reporter: Chris Rankin
> Attachments: arquillian-test.tar.xz
>
>
> Using arquillian-tomcat-embedded-7, arquillian-bom 1.1.7.Final, WELD 2.2.10.Final:
> I have created a simple WAR file that contains WELD and a single servlet. There is also a dependent JAR that contains the following:
> - a @Dependent bean with a @Produces method
> - a META-INF/beans.xml file.
> When I try to test this servlet using Arquillian's TestNG container, the deployment fails with this error:
> SEVERE: Servlet threw load() exception
> org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type String with qualifiers @Trouble
> at injection point [BackedAnnotatedField] @Trouble @Inject private org.testing.web.TroubleServlet.trouble
> at org.testing.web.TroubleServlet.trouble(TroubleServlet.java:0)
> Possible dependencies:
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()],
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARQ-1943) Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when beans inside a dependent JAR.
by Chris Rankin (JIRA)
[ https://issues.jboss.org/browse/ARQ-1943?page=com.atlassian.jira.plugin.s... ]
Chris Rankin commented on ARQ-1943:
-----------------------------------
Could this be related to WELD-1658?
> Deployment fails with WELD >= 2.2.5.Final because of duplicate CDI beans when beans inside a dependent JAR.
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1943
> URL: https://issues.jboss.org/browse/ARQ-1943
> Project: Arquillian
> Issue Type: Bug
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Environment: Windows 7 x64, Linux x64, JDK7
> Reporter: Chris Rankin
> Attachments: arquillian-test.tar.xz
>
>
> Using arquillian-tomcat-embedded-7, arquillian-bom 1.1.7.Final, WELD 2.2.10.Final:
> I have created a simple WAR file that contains WELD and a single servlet. There is also a dependent JAR that contains the following:
> - a @Dependent bean with a @Produces method
> - a META-INF/beans.xml file.
> When I try to test this servlet using Arquillian's TestNG container, the deployment fails with this error:
> SEVERE: Servlet threw load() exception
> org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type String with qualifiers @Trouble
> at injection point [BackedAnnotatedField] @Trouble @Inject private org.testing.web.TroubleServlet.trouble
> at org.testing.web.TroubleServlet.trouble(TroubleServlet.java:0)
> Possible dependencies:
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()],
> - Producer Method [String] with qualifiers [@Trouble @Any] declared as [[BackedAnnotatedMethod] @Produces @Trouble org.testing.TroubleMaker.getTrouble()]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months