[JBoss JIRA] (ARQ-1924) Bad behaviour on Shrinkwrap.addAsServiceProvider
by Antonin Stefanutti (JIRA)
[ https://issues.jboss.org/browse/ARQ-1924?page=com.atlassian.jira.plugin.s... ]
Antonin Stefanutti edited comment on ARQ-1924 at 4/21/15 4:45 AM:
------------------------------------------------------------------
I've been reproducing the same issue in https://github.com/astefanutti/further-cdi/blob/b490b41747b70b0e5a28f05ba....
In my case, the extension added with {{addAsServiceProvider}} is not deployed by the CDI container managed by the {{arquillian-weld-ee-embedded-1.1}} adapter when I create an EAR, while that works when I create a WAR.
As mentioned in the description, the extension is deployed as expected in the CDI container managed by the {{wildfly-arquillian-container-managed}} adapter.
I'd suggest to update the title to be more specific so that users don't lose too much time trying to troubleshoot why extensions are not properly deployed when being added with {{addAsServiceProvider}}.
was (Author: stefanutti):
I've been facing the same issue in https://github.com/astefanutti/further-cdi/blob/b490b41747b70b0e5a28f05ba....
In my case, the extension added with {{addAsServiceProvider}} is not deployed by the CDI container managed by the {{arquillian-weld-ee-embedded-1.1}} adapter when I create an EAR, while that works when I create a WAR.
As mentioned in the description, the extension is deployed as expected in the CDI container managed by the {{wildfly-arquillian-container-managed}} adapter.
I'd suggest to update the title to be more specific so that users don't lose too much time trying to troubleshoot why extensions are not properly deployed when being added with {{addAsServiceProvider}}.
> Bad behaviour on Shrinkwrap.addAsServiceProvider
> ------------------------------------------------
>
> Key: ARQ-1924
> URL: https://issues.jboss.org/browse/ARQ-1924
> Project: Arquillian
> Issue Type: Bug
> Components: OpenWebBeans Containers, Weld Containers
> Affects Versions: 1.0.0.CR8, 1.1.7.Final
> Reporter: Rafael Benevides
> Attachments: arquillian-test.zip
>
>
> The attached maven project contains two tests:
> 1 - ExtensionInJarTest - This adds a Service through .addAsServiceProvider to an JAR that is placed inside a WAR
> 2 - ExtensionInWarTest - This add a Service through .addAsServiceProvider directly to a WAR
> If you run the tests inside Wildfly:
> {code}
> mvn clean test -Parq-wildfly-remote //it works
> {code}
> If you run the tests using Weld or OWB:
> {code}
> mvn clean test -PWeld //it fails on ExtensionInJarTest
> mvn clean test -POWB //it fails on ExtensionInJarTest
> {code}
> The expected behaviour is that Weld and OWB shouldn't fail.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (ARQ-1924) Bad behaviour on Shrinkwrap.addAsServiceProvider
by Antonin Stefanutti (JIRA)
[ https://issues.jboss.org/browse/ARQ-1924?page=com.atlassian.jira.plugin.s... ]
Antonin Stefanutti commented on ARQ-1924:
-----------------------------------------
I've been facing the same issue in https://github.com/astefanutti/further-cdi/blob/b490b41747b70b0e5a28f05ba....
In my case, the extension added with {{addAsServiceProvider}} is not deployed by the CDI container managed by the {{arquillian-weld-ee-embedded-1.1}} adapter when I create an EAR, while that works when I create a WAR.
As mentioned in the description, the extension is deployed as expected in the CDI container managed by the {{wildfly-arquillian-container-managed}} adapter.
I'd suggest to update the title to be more specific so that users don't lose too much time trying to troubleshoot why extensions are not properly deployed when being added with {{addAsServiceProvider}}.
> Bad behaviour on Shrinkwrap.addAsServiceProvider
> ------------------------------------------------
>
> Key: ARQ-1924
> URL: https://issues.jboss.org/browse/ARQ-1924
> Project: Arquillian
> Issue Type: Bug
> Components: OpenWebBeans Containers, Weld Containers
> Affects Versions: 1.0.0.CR8, 1.1.7.Final
> Reporter: Rafael Benevides
> Attachments: arquillian-test.zip
>
>
> The attached maven project contains two tests:
> 1 - ExtensionInJarTest - This adds a Service through .addAsServiceProvider to an JAR that is placed inside a WAR
> 2 - ExtensionInWarTest - This add a Service through .addAsServiceProvider directly to a WAR
> If you run the tests inside Wildfly:
> {code}
> mvn clean test -Parq-wildfly-remote //it works
> {code}
> If you run the tests using Weld or OWB:
> {code}
> mvn clean test -PWeld //it fails on ExtensionInJarTest
> mvn clean test -POWB //it fails on ExtensionInJarTest
> {code}
> The expected behaviour is that Weld and OWB shouldn't fail.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (ARQ-1943) Deployment fails with weld-servlet >= 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-servlet >= 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 deployment contains bean archive)
> Deployment fails with weld-servlet >= 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
[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 commented on ARQ-1943:
-----------------------------------
[The plot thickens|https://docs.jboss.org/weld/reference/latest/en-US/html/environm...]:
{quote}In general, an implicit bean archive does not have to contain a beans.xml descriptor. However, such a bean archive is not supported by Weld Servlet, i.e. it’s excluded from discovery.{quote}
My Tomcat is indeed using Weld Servlet, which means my bean archive _must_ contain a {{beans.xml}} descriptor. And toggling the {{org.jboss.weld.environment.servlet.archive.isolation}} context parameter has the following effect:
|| {{org.jboss.weld.environment.servlet.archive.isolation}} || Bean instances ||
| true | 2 |
| false | 0 |
> 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
[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 closed ARQ-1936.
------------------------------
> 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
> Assignee: Aslak Knutsen
> Fix For: jacoco_1.0.0.Alpha8
>
>
> 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
[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.Alpha8
(was: 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
> Assignee: Aslak Knutsen
> Fix For: jacoco_1.0.0.Alpha8
>
>
> 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
[JBoss JIRA] (ARQ-1479) NoSuchMethodError with weld se container and junit continer 1.1.1
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/ARQ-1479?page=com.atlassian.jira.plugin.s... ]
Romain Pelisse commented on ARQ-1479:
-------------------------------------
Hi,
I hate to be the one reopening issue, but I've more/less follow the Arquillian tutorial, and I ran in the same issue, that I've resolved using Scott Starke proposed workaround. If you want to reproduce it, simply checkout out the following branch on my github account:
https://github.com/rpelisse/Belarquian/tree/ARQ-1479
> NoSuchMethodError with weld se container and junit continer 1.1.1
> -----------------------------------------------------------------
>
> Key: ARQ-1479
> URL: https://issues.jboss.org/browse/ARQ-1479
> Project: Arquillian
> Issue Type: Bug
> Components: Weld Containers
> Affects Versions: weld_1.0.0.CR7
> Reporter: Shay Matasaro
> Assignee: Aslak Knutsen
>
> when using the weld-se 1.0.0.cr7 container with junit 1.1.1 container an exception is thrown:
> java.lang.NoSuchMethodError: org.jboss.arquillian.container.spi.client.deployment.Validate.archiveHasExpectedFileExtension(Lorg/jboss/shrinkwrap/api/Archive;)Z
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.logWarningIfArchiveHasUnexpectedFileExtension(AnnotationDeploymentScenarioGenerator.java:130)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:100)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62)
> at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[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 resolved ARQ-1936.
--------------------------------
Assignee: Aslak Knutsen
Resolution: Done
upstream https://github.com/arquillian/arquillian-extension-jacoco/commit/11593297...
> 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
> Assignee: Aslak Knutsen
> 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