From issues at jboss.org Sat Nov 1 13:40:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 13:40:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: John Ament created ARQ-1875: ------------------------------- Summary: JaCoCo extension only works for simple use cases Key: ARQ-1875 URL: https://issues.jboss.org/browse/ARQ-1875 Project: Arquillian Issue Type: Bug Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha7 Reporter: John Ament In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. Here's an example output: {quote} Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) ... 28 more 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"stratas-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] {quote} My jboss-deployment-structure.xml looks like this: {code} {code} Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Nov 1 13:53:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 13:53:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated ARQ-1875: ---------------------------- Description: In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. Here's an example output: {quote} Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) ... 28 more 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] {quote} My jboss-deployment-structure.xml looks like this: {code} {code} Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. was: In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. Here's an example output: {quote} Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) ... 28 more 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"stratas-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.reflect.UndeclaredThrowableException Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] {quote} My jboss-deployment-structure.xml looks like this: {code} {code} Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Nov 1 13:53:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 13:53:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016570#comment-13016570 ] John Ament commented on ARQ-1875: --------------------------------- Actually digging in more makes it look like a CXF/ASM/JaCoCo issue. Here's the full stack: {quote} 3:34:21,012 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."api-webapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."api-webapp.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "api-webapp.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.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_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20] Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:137) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:69) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] ... 5 more Caused by: java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy71.visitLabel(Unknown Source) at org.apache.cxf.jaxws.WrapperClassGenerator.createWrapperClass(WrapperClassGenerator.java:213) at org.apache.cxf.jaxws.WrapperClassGenerator.generate(WrapperClassGenerator.java:122) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.generatedWrapperBeanClass(JaxWsServiceFactoryBean.java:683) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.getExtraClass(JaxWsServiceFactoryBean.java:653) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:484) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:704) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:550) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:265) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:215) at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102) at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159) at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211) at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:456) at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:334) ... 13 more {quote} > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Nov 1 15:31:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 15:31:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016572#comment-13016572 ] John Ament commented on ARQ-1875: --------------------------------- Here's a simple test case that reproduces the issue: https://github.com/johnament/arquillian-extension-jacoco/commit/bc4632086a5d601c12bad468cbbf6a6180c582ef > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Nov 1 20:03:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 20:03:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016573#comment-13016573 ] John Ament commented on ARQ-1875: --------------------------------- Ok, so I have raised a PR to "fix" this. Fix is a loose term here. i'm working around the issue by having Arquillian use a repack of JaCoCo that puts ASM into a different directory. Thereby removing the conflict. https://github.com/arquillian/arquillian-extension-jacoco/pull/16 > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Nov 1 20:04:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sat, 1 Nov 2014 20:04:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated ARQ-1875: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/16 > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sun Nov 2 08:10:35 2014 From: issues at jboss.org (Leonardo Loch Zanivan (JIRA)) Date: Sun, 2 Nov 2014 08:10:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016576#comment-13016576 ] Leonardo Loch Zanivan commented on ARQ-1875: -------------------------------------------- I'm using Arquillian JaCoCo 1.0.0.Alpha7 with JDK 8u20 and WildFly 8.1.0.Final in a couple of web apps and I didn't had any issue. They're Java EE 7 web apps which uses JAX-RS, EJB, JPA, but no WS. IMHO I think it's a WildFly component issue, it's supposed to run with Java 8 and will cause other compatibility issues with libraries which requires ASM 5+. > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sun Nov 2 18:42:35 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Sun, 2 Nov 2014 18:42:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated ARQ-1875: ---------------------------- Status: Open (was: Pull Request Sent) > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 08:15:38 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Nov 2014 08:15:38 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1876) Investigate collapsable entries In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1876: -------------------------------------- Summary: Investigate collapsable entries Key: ARQ-1876 URL: https://issues.jboss.org/browse/ARQ-1876 Project: Arquillian Issue Type: Feature Request Components: Extension - Recorder Affects Versions: recorder_1.0.0.Beta1 Reporter: Stefan Miklosovic Priority: Optional Only long exception stacks are done collapsable, try to do it on entry level in general. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 08:16:35 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Nov 2014 08:16:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1877) PropertyEntry.getProperties doesn't seem to be rendered recursivly In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1877: -------------------------------------- Summary: PropertyEntry.getProperties doesn't seem to be rendered recursivly Key: ARQ-1877 URL: https://issues.jboss.org/browse/ARQ-1877 Project: Arquillian Issue Type: Bug Components: Extension - Recorder Affects Versions: recorder_1.0.0.Beta1 Reporter: Stefan Miklosovic -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 08:18:35 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Nov 2014 08:18:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1878) Introduce TableEntry In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1878: -------------------------------------- Summary: Introduce TableEntry Key: ARQ-1878 URL: https://issues.jboss.org/browse/ARQ-1878 Project: Arquillian Issue Type: Enhancement Components: Extension - Recorder Affects Versions: recorder_1.0.0.Beta1 Reporter: Stefan Miklosovic Priority: Optional TableEntry should have header, rows and cells. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Nov 5 04:31:35 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 5 Nov 2014 04:31:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1879) Remove dependency on TCCL in JUnitBundleTestRunner In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1879: ----------------------------------- Summary: Remove dependency on TCCL in JUnitBundleTestRunner Key: ARQ-1879 URL: https://issues.jboss.org/browse/ARQ-1879 Project: Arquillian Issue Type: Bug Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Currently the JUnitBundleTestRunner uses code like this {code} public TestResult execute(Class testClass, String methodName) { ClassLoader ctxLoader = Thread.currentThread().getContextClassLoader(); try { // Make sure we run in the context of the arquillian-bundle class loader Thread.currentThread().setContextClassLoader(getClass().getClassLoader()); return super.execute(testClass, methodName); } finally { Thread.currentThread().setContextClassLoader(ctxLoader); } } {code} This causes issues with APIs that use the TCCL for resource discovery. Investigate why the TCCL is used at all and whether the testClass CL could be used instead -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Nov 6 02:33:30 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Thu, 6 Nov 2014 02:33:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1880) Arquillian core relies on TCCL to load infra In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1880: ----------------------------------- Summary: Arquillian core relies on TCCL to load infra Key: ARQ-1880 URL: https://issues.jboss.org/browse/ARQ-1880 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.1.2.Final Reporter: Thomas Diesler While testing FSW product stuff it turns out that test code is executed with a TCCL from the ARQ bundle. If ARQ does not set a TCCL we get {code} Caused by: java.lang.ClassNotFoundException: org/jboss/arquillian/test/impl/EventTestRunnerAdaptor at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:270) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:105) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97) at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at org.junit.runner.JUnitCore.run(JUnitCore.java:138) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) at org.jboss.arquillian.osgi.JUnitBundleTestRunner.execute(JUnitBundleTestRunner.java:34) {code} Having a TCCL set is highly problematic in OSGi because it bypasses al user defined wiring rules. When test code calls into API that uses TCCL, that API will try to load types from the ARQ Bundle classloader, which of course has no visibility to the requested types/resources. The ARQ infra should ideally not have to depend on TCCL for loading its own types. Second best would be to reset the TCCL after all infra stuff is done and before the call into the test case. The TCCL association is part of the public API. From the perspective of the test case, it needs to be defined and ideally be guaranteed to be null. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 02:34:29 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Thu, 6 Nov 2014 02:34:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1880) Arquillian core relies on TCCL to load infra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1880: -------------------------------- Component/s: (was: Runtime Enricher SPI) > Arquillian core relies on TCCL to load infra > -------------------------------------------- > > Key: ARQ-1880 > URL: https://issues.jboss.org/browse/ARQ-1880 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > > While testing FSW product stuff it turns out that test code is executed with a TCCL from the ARQ bundle. If ARQ does not set a TCCL we get > {code} > Caused by: java.lang.ClassNotFoundException: org/jboss/arquillian/test/impl/EventTestRunnerAdaptor > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:105) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.osgi.JUnitBundleTestRunner.execute(JUnitBundleTestRunner.java:34) > {code} > Having a TCCL set is highly problematic in OSGi because it bypasses al user defined wiring rules. When test code calls into API that uses TCCL, that API will try to load types from the ARQ Bundle classloader, which of course has no visibility to the requested types/resources. > The ARQ infra should ideally not have to depend on TCCL for loading its own types. Second best would be to reset the TCCL after all infra stuff is done and before the call into the test case. > The TCCL association is part of the public API. From the perspective of the test case, it needs to be defined and ideally be guaranteed to be null. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 03:58:20 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 6 Nov 2014 03:58:20 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1881) Fix starting/stopping of remote karaf container In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1881: ------------------------------------ Summary: Fix starting/stopping of remote karaf container Key: ARQ-1881 URL: https://issues.jboss.org/browse/ARQ-1881 Project: Arquillian Issue Type: Bug Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Conditions to start and stop remote karaf container are not properly set. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 04:01:29 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 6 Nov 2014 04:01:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1881) Fix starting/stopping of remote karaf container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1881: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/36 > Fix starting/stopping of remote karaf container > ----------------------------------------------- > > Key: ARQ-1881 > URL: https://issues.jboss.org/browse/ARQ-1881 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Conditions to start and stop remote karaf container are not properly set. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:25:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Nov 2014 12:25:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1878) Introduce TableEntry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1878: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/11 > Introduce TableEntry > -------------------- > > Key: ARQ-1878 > URL: https://issues.jboss.org/browse/ARQ-1878 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Beta1 > Reporter: Stefan Miklosovic > Priority: Optional > > TableEntry should have header, rows and cells. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 02:35:29 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 7 Nov 2014 02:35:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1882: -------------------------------- Summary: NPE in ConfigurationMapper Key: ARQ-1882 URL: https://issues.jboss.org/browse/ARQ-1882 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_1.3.1.Final, drone_2.0.0.Alpha2 Reporter: Karel Piwko If there is no Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 05:07:30 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 7 Nov 2014 05:07:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1882: ----------------------------- Description: If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax (was: If there is no Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax) > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 05:08:30 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 7 Nov 2014 05:08:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1882. ------------------------------ Fix Version/s: drone_1.3.2.Final drone_2.0.0.Alpha3 Resolution: Done > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > Fix For: drone_1.3.2.Final, drone_2.0.0.Alpha3 > > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 05:08:30 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 7 Nov 2014 05:08:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018181#comment-13018181 ] Karel Piwko commented on ARQ-1882: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/tree/drone_1.3.x and https://github.com/arquillian/arquillian-extension-drone/commit/5384178f67da358e211a72d0cc43d928f1fff81e > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha3, drone_1.3.2.Final > > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 9 09:28:29 2014 From: issues at jboss.org (Rafael Pestano (JIRA)) Date: Sun, 9 Nov 2014 09:28:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1883) Arquillian Persistence Extension: Cucumber integration In-Reply-To: References: Message-ID: Rafael Pestano created ARQ-1883: ----------------------------------- Summary: Arquillian Persistence Extension: Cucumber integration Key: ARQ-1883 URL: https://issues.jboss.org/browse/ARQ-1883 Project: Arquillian Issue Type: Feature Request Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Rafael Pestano Assignee: Bartosz Majsak Currently we cannot use persistence extension in a Cucumber test. Cukespace extension added events that other extensions can observe in order to e.g.: do something before a step. see this issue for more details: https://github.com/cukespace/cukespace/issues/37 Also there this blog post which details the limitations of using both extensions: http://rpestano.wordpress.com/2014/11/08/arquillian-cucumber-dbunit/ -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 9 10:07:30 2014 From: issues at jboss.org (Romain Manni-Bucau (JIRA)) Date: Sun, 9 Nov 2014 10:07:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1883) Arquillian Persistence Extension: Cucumber integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018474#comment-13018474 ] Romain Manni-Bucau commented on ARQ-1883: ----------------------------------------- basic support here https://github.com/cukespace/cukespace/commit/69573686353cd46154bdb6a34a6f3f79086edf59 (misses a test in cukespace + some reflection could be avoided but that's a start. PR welcomed ;)) > Arquillian Persistence Extension: Cucumber integration > ------------------------------------------------------ > > Key: ARQ-1883 > URL: https://issues.jboss.org/browse/ARQ-1883 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Rafael Pestano > Assignee: Bartosz Majsak > > Currently we cannot use persistence extension in a Cucumber test. > Cukespace extension added events that other extensions can observe in order to e.g.: do something before a step. > see this issue for more details: https://github.com/cukespace/cukespace/issues/37 > Also there this blog post which details the limitations of using both extensions: http://rpestano.wordpress.com/2014/11/08/arquillian-cucumber-dbunit/ -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 10 09:22:29 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Nov 2014 09:22:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1884) Update Selenium to 2.44.0 In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1884: -------------------------------- Summary: Update Selenium to 2.44.0 Key: ARQ-1884 URL: https://issues.jboss.org/browse/ARQ-1884 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_1.3.1.Final, drone_2.0.0.Alpha2 Reporter: Karel Piwko -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:49 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Nov 2014 09:36:49 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1885) Droidium is not buildable with Java 8 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1885: -------------------------------------- Summary: Droidium is not buildable with Java 8 Key: ARQ-1885 URL: https://issues.jboss.org/browse/ARQ-1885 Project: Arquillian Issue Type: Bug Components: Extension - Droidium Affects Versions: droidium_1.0.0.Beta1 Reporter: Stefan Miklosovic {code} ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (signature-check) on project arquillian-droidium-container: Execution signature-check of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (signature-check) on project arquillian-droidium-container: Execution signature-check of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. ... Caused by: java.lang.IllegalArgumentException at org.objectweb.asm.ClassReader.(Unknown Source) at org.objectweb.asm.ClassReader.(Unknown Source) at org.objectweb.asm.ClassReader.(Unknown Source) {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 03:01:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 12 Nov 2014 03:01:11 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1885) Droidium is not buildable with Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1885. ------------------------------------ Assignee: Stefan Miklosovic Fix Version/s: droidium_1.0.0.Beta1 Resolution: Done There has to be new version of asm (5.0.3) with Java 8. > Droidium is not buildable with Java 8 > ------------------------------------- > > Key: ARQ-1885 > URL: https://issues.jboss.org/browse/ARQ-1885 > Project: Arquillian > Issue Type: Bug > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Beta1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > {code} > ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (signature-check) on project arquillian-droidium-container: Execution signature-check of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (signature-check) on project arquillian-droidium-container: Execution signature-check of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. > ... > Caused by: java.lang.IllegalArgumentException > at org.objectweb.asm.ClassReader.(Unknown Source) > at org.objectweb.asm.ClassReader.(Unknown Source) > at org.objectweb.asm.ClassReader.(Unknown Source) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 06:38:29 2014 From: issues at jboss.org (Anonymous (JIRA)) Date: Wed, 12 Nov 2014 06:38:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-61) Umbrella: Rename the project to Graphene In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019303#comment-13019303 ] Anonymous commented on ARQGRA-61: --------------------------------- Apart from that, number of obvious some useless and redundant files, which can left over by the uninstalled programs in the registry. Are usually also in charge of overloading the memory on account of your system swallows a lot time to notice that these programs cannot be loaded. While doing this long span of time various other start up programs stand it queue. [url=http://seecofneeq.com/wp-content/PC-Cleaner/]windows 8 restore[/url] > Umbrella: Rename the project to Graphene > ---------------------------------------- > > Key: ARQGRA-61 > URL: https://issues.jboss.org/browse/ARQGRA-61 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 1.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 07:56:30 2014 From: issues at jboss.org (=?UTF-8?Q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29?=) Date: Wed, 12 Nov 2014 07:56:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-61) Umbrella: Rename the project to Graphene In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlastimil Eli?? updated ARQGRA-61: ---------------------------------- Comment: was deleted (was: Apart from that, number of obvious some useless and redundant files, which can left over by the uninstalled programs in the registry. Are usually also in charge of overloading the memory on account of your system swallows a lot time to notice that these programs cannot be loaded. While doing this long span of time various other start up programs stand it queue. [url=http://seecofneeq.com/wp-content/PC-Cleaner/]windows 8 restore[/url]) > Umbrella: Rename the project to Graphene > ---------------------------------------- > > Key: ARQGRA-61 > URL: https://issues.jboss.org/browse/ARQGRA-61 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 1.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sat Nov 15 14:16:39 2014 From: issues at jboss.org (Peter Butkovic (JIRA)) Date: Sat, 15 Nov 2014 14:16:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1789) Add tomcat 8 managed and remote container adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020313#comment-13020313 ] Peter Butkovic commented on ARQ-1789: ------------------------------------- [~aslak] you were right. I gave it a try and managed 7 worked for me with tomcat 8.0.15! Feel free to close the issue, as it's not relevant for me any more. > Add tomcat 8 managed and remote container adapters > -------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Peter Butkovic > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sat Nov 15 19:31:39 2014 From: issues at jboss.org (Ian Brandt (JIRA)) Date: Sat, 15 Nov 2014 19:31:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1789) Add tomcat 8 managed and remote container adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020316#comment-13020316 ] Ian Brandt commented on ARQ-1789: --------------------------------- [~typek_pb]: Glad managed-7 is working for you. I'm still planning to add an explicit managed-8 container when I get a chance. That way we'll have test coverage and clear documentation for Tomcat 8 support. My plan is to merge the ARQ-1848 branch down to master first, and then base it off that. > Add tomcat 8 managed and remote container adapters > -------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Peter Butkovic > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Sun Nov 16 05:01:39 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 16 Nov 2014 05:01:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1789) Add tomcat 8 managed and remote container adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020319#comment-13020319 ] Aslak Knutsen commented on ARQ-1789: ------------------------------------ [~ianbrandt] Maybe all we need here is a 'proxy' pom that include the 7 adapter? > Add tomcat 8 managed and remote container adapters > -------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Peter Butkovic > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 04:52:39 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 19 Nov 2014 04:52:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1886) Support remote containers on remote hosts In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1886: ----------------------------------- Summary: Support remote containers on remote hosts Key: ARQ-1886 URL: https://issues.jboss.org/browse/ARQ-1886 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Remote container support is currently limited to separate JVMs with a shared filesystem. This change allows containers on remote hosts to be supported by serving bundles to be installed in the container using a simple (single class) HTTP server. We've been using this approach in our Arquillian fork since 2012 and it's worked well. Also updated docs to include current set of containers, and to note that the Apache Karaf remote container actually works with any OSGi Enterprise JMX enabled container (we use Apache Aries JMX in an Equinox container). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 02:16:39 2014 From: issues at jboss.org (=?UTF-8?Q?Arkadiusz_Gasi=C5=84ski_=28JIRA=29?=) Date: Thu, 20 Nov 2014 02:16:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1887) SQL scripts and ANSI_SQL_COMMENTS_PATTERN - unable to insert URL In-Reply-To: References: Message-ID: Arkadiusz Gasi?ski created ARQ-1887: --------------------------------------- Summary: SQL scripts and ANSI_SQL_COMMENTS_PATTERN - unable to insert URL Key: ARQ-1887 URL: https://issues.jboss.org/browse/ARQ-1887 Project: Arquillian Issue Type: Feature Request Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Arkadiusz Gasi?ski Assignee: Bartosz Majsak Unable to insert URLs using @ApplyScriptBefore - example below. {code:title=sample.sql|borderStyle=solid} INSERT INTO CONFIG(NAME, MODULE, VALUE) VALUES('core.url', 'isep-core-tck', 'http://localhost:41080/BusinessLogicVersioningTest/api/v1'); {code} Setting showSql to true in persistence-script extension configuration in arquillian.xml produces the following output: {code:title=output.log|borderStyle=solid} INSERT INTO CONFIG(NAME, MODULE, VALUE) VALUES('core.url', 'isep-core-tck', 'http: {code} The double slash (//) after the protocol is treated as a comment and thus the rest of the statement is ignored. Shouldn't the // character sequence be treated as a comment only if it's placed at the beginning of a line? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 03:58:39 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 20 Nov 2014 03:58:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1887) SQL scripts and ANSI_SQL_COMMENTS_PATTERN - unable to insert URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021433#comment-13021433 ] Bartosz Majsak commented on ARQ-1887: ------------------------------------- Ouch that's a silly one :) Many thanks for the detailed report. I will have a closer look. > SQL scripts and ANSI_SQL_COMMENTS_PATTERN - unable to insert URL > ---------------------------------------------------------------- > > Key: ARQ-1887 > URL: https://issues.jboss.org/browse/ARQ-1887 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Arkadiusz Gasi?ski > Assignee: Bartosz Majsak > > Unable to insert URLs using @ApplyScriptBefore - example below. > {code:title=sample.sql|borderStyle=solid} > INSERT INTO CONFIG(NAME, MODULE, VALUE) VALUES('core.url', 'isep-core-tck', 'http://localhost:41080/BusinessLogicVersioningTest/api/v1'); > {code} > Setting showSql to true in persistence-script extension configuration in arquillian.xml produces the following output: > {code:title=output.log|borderStyle=solid} > INSERT INTO CONFIG(NAME, MODULE, VALUE) VALUES('core.url', 'isep-core-tck', 'http: > {code} > The double slash (//) after the protocol is treated as a comment and thus the rest of the statement is ignored. > Shouldn't the // character sequence be treated as a comment only if it's placed at the beginning of a line? -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 12:46:39 2014 From: issues at jboss.org (Jiri Locker (JIRA)) Date: Thu, 20 Nov 2014 12:46:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1888) IE driver 2.43+ fails to start due to missing capabilities type mapping In-Reply-To: References: Message-ID: Jiri Locker created ARQ-1888: -------------------------------- Summary: IE driver 2.43+ fails to start due to missing capabilities type mapping Key: ARQ-1888 URL: https://issues.jboss.org/browse/ARQ-1888 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_1.3.1.Final Reporter: Jiri Locker Priority: Critical IE driver became sensitive to capabilities data types in version 2.43.0. If a capability has an unexpected type (e.g. Boolean capability with String value "true"), the driver will fail on the first command, which is obviously an absolute show stopper. [Issue 8160|https://code.google.com/p/selenium/issues/detail?id=8160] has been filed in Selenium project. A fix has been made on master which prevents IE driver from crashing but wrongly typed capabilities will fall back to default values. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 13:25:39 2014 From: issues at jboss.org (Jiri Locker (JIRA)) Date: Thu, 20 Nov 2014 13:25:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1888) IE driver 2.43+ fails to start due to missing capabilities type mapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Locker updated ARQ-1888: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/45 > IE driver 2.43+ fails to start due to missing capabilities type mapping > ----------------------------------------------------------------------- > > Key: ARQ-1888 > URL: https://issues.jboss.org/browse/ARQ-1888 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Jiri Locker > Priority: Critical > > IE driver became sensitive to capabilities data types in version 2.43.0. If a capability has an unexpected type (e.g. Boolean capability with String value "true"), the driver will fail on the first command, which is obviously an absolute show stopper. > [Issue 8160|https://code.google.com/p/selenium/issues/detail?id=8160] has been filed in Selenium project. A fix has been made on master which prevents IE driver from crashing but wrongly typed capabilities will fall back to default values. -- This message was sent by Atlassian JIRA (v6.3.8#6338)