March 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1936) Jacoco Extension needs signature removal

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/ARQ-1936?page=com.atlassian.jira.plugin.s... ] Arcadiy Ivanov updated ARQ-1936: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/19 > 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 > > 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 an 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1936) Jacoco Extension needs signature removal

by Arcadiy Ivanov (JIRA)

Arcadiy Ivanov created ARQ-1936: ----------------------------------- Summary: 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 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 an 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-468: ----------------------------------- Yea, I'm sorry for ambiguity :-) I meant Pull Request > Cannot use relative @Location when using "standalone" JUnit integration > ----------------------------------------------------------------------- > > Key: ARQGRA-468 > URL: https://issues.jboss.org/browse/ARQGRA-468 > Project: Arquillian Graphene > Issue Type: Bug > Components: configuration > Affects Versions: 2.1.0.Alpha2 > Reporter: Christoffer Bromberg > Priority: Minor > > As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL. > This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > After I switched to the "container" dependency it works as expected. > I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the > {code} >  > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <scope>test</scope> > </dependency> > {code} > dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed. > So the workaround for me was to use the arquillian-junit-container dependency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

by Christoffer Bromberg (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin... ] Christoffer Bromberg commented on ARQGRA-468: --------------------------------------------- You mean PR like Pull Request, hah - I was thinking Problem Report. Ok, I'll do my best > Cannot use relative @Location when using "standalone" JUnit integration > ----------------------------------------------------------------------- > > Key: ARQGRA-468 > URL: https://issues.jboss.org/browse/ARQGRA-468 > Project: Arquillian Graphene > Issue Type: Bug > Components: configuration > Affects Versions: 2.1.0.Alpha2 > Reporter: Christoffer Bromberg > Priority: Minor > > As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL. > This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > After I switched to the "container" dependency it works as expected. > I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the > {code} >  > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <scope>test</scope> > </dependency> > {code} > dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed. > So the workaround for me was to use the arquillian-junit-container dependency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin... ] Lukáš Fryč edited comment on ARQGRA-468 at 3/19/15 6:43 AM: ------------------------------------------------------------ As described in https://developer.jboss.org/message/922128#922128 I believe we should just make the CustomizableURLResourceProvider independent from URLResourceProvider and delegate when required (in-container). was (Author: lfryc): As described in https://developer.jboss.org/message/922128#922128 I believe we should just make the CustomizableURLResourceProvider independently from URLResourceProvider and delegate to it when required. > Cannot use relative @Location when using "standalone" JUnit integration > ----------------------------------------------------------------------- > > Key: ARQGRA-468 > URL: https://issues.jboss.org/browse/ARQGRA-468 > Project: Arquillian Graphene > Issue Type: Bug > Components: configuration > Affects Versions: 2.1.0.Alpha2 > Reporter: Christoffer Bromberg > Priority: Minor > > As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL. > This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > After I switched to the "container" dependency it works as expected. > I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the > {code} >  > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <scope>test</scope> > </dependency> > {code} > dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed. > So the workaround for me was to use the arquillian-junit-container dependency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-468: ----------------------------------- [~christoffer] do you fancy opening a PR? > Cannot use relative @Location when using "standalone" JUnit integration > ----------------------------------------------------------------------- > > Key: ARQGRA-468 > URL: https://issues.jboss.org/browse/ARQGRA-468 > Project: Arquillian Graphene > Issue Type: Bug > Components: configuration > Affects Versions: 2.1.0.Alpha2 > Reporter: Christoffer Bromberg > Priority: Minor > > As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL. > This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > After I switched to the "container" dependency it works as expected. > I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the > {code} >  > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <scope>test</scope> > </dependency> > {code} > dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed. > So the workaround for me was to use the arquillian-junit-container dependency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-468: ----------------------------------- As described in https://developer.jboss.org/message/922128#922128 I believe we should just make the CustomizableURLResourceProvider independently from URLResourceProvider and delegate to it when required. > Cannot use relative @Location when using "standalone" JUnit integration > ----------------------------------------------------------------------- > > Key: ARQGRA-468 > URL: https://issues.jboss.org/browse/ARQGRA-468 > Project: Arquillian Graphene > Issue Type: Bug > Components: configuration > Affects Versions: 2.1.0.Alpha2 > Reporter: Christoffer Bromberg > Priority: Minor > > As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL. > This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > After I switched to the "container" dependency it works as expected. > I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the > {code} >  > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <scope>test</scope> > </dependency> > {code} > dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed. > So the workaround for me was to use the arquillian-junit-container dependency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1928) Update Droidium to use Arquillian Recorder 1.0.0.Final

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1928?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1928. ---------------------------------- > Update Droidium to use Arquillian Recorder 1.0.0.Final > ------------------------------------------------------ > > Key: ARQ-1928 > URL: https://issues.jboss.org/browse/ARQ-1928 > Project: Arquillian > Issue Type: Task > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha6 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1934) Update Droidium to use Drone 2.0.0.Alpha4

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1934?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1934. ---------------------------------- > Update Droidium to use Drone 2.0.0.Alpha4 > ----------------------------------------- > > Key: ARQ-1934 > URL: https://issues.jboss.org/browse/ARQ-1934 > Project: Arquillian > Issue Type: Task > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha6 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1928) Update Droidium to use Arquillian Recorder 1.0.0.Final

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1928?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1928: ----------------------------------- Fix Version/s: droidium_1.0.0.Final > Update Droidium to use Arquillian Recorder 1.0.0.Final > ------------------------------------------------------ > > Key: ARQ-1928 > URL: https://issues.jboss.org/browse/ARQ-1928 > Project: Arquillian > Issue Type: Task > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha6 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2015