From issues at jboss.org Thu Feb 2 08:49:00 2017 From: issues at jboss.org (Vojtech Juranek (JIRA)) Date: Thu, 2 Feb 2017 08:49:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2071) Use save function for checking if tomcat is running In-Reply-To: References: Message-ID: Vojtech Juranek created ARQ-2071: ------------------------------------ Summary: Use save function for checking if tomcat is running Key: ARQ-2071 URL: https://issues.jboss.org/browse/ARQ-2071 Project: Arquillian Issue Type: Enhancement Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR8 Reporter: Vojtech Juranek Currently AQR use {{list}} method of tomcat manager to find out if container is running. However, some session manager may not support this operation (e.g. because of security reasons or other). In such case ARQ fails to start tomcat. It would be nice to use some more safe method, which will be very likely implemented everwhere, e.g. {{serverinfo}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 2 08:57:00 2017 From: issues at jboss.org (Vojtech Juranek (JIRA)) Date: Thu, 2 Feb 2017 08:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2071) Use save function for checking if tomcat is running In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vojtech Juranek updated ARQ-2071: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/37 > Use save function for checking if tomcat is running > --------------------------------------------------- > > Key: ARQ-2071 > URL: https://issues.jboss.org/browse/ARQ-2071 > Project: Arquillian > Issue Type: Enhancement > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR8 > Reporter: Vojtech Juranek > > Currently AQR use {{list}} method of tomcat manager to find out if container is running. However, some session manager may not support this operation (e.g. because of security reasons or other). In such case ARQ fails to start tomcat. It would be nice to use some more safe method, which will be very likely implemented everwhere, e.g. {{serverinfo}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 2 11:28:01 2017 From: issues at jboss.org (Vojtech Juranek (JIRA)) Date: Thu, 2 Feb 2017 11:28:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2072) Tomcat fails to start if cataliBase is not set In-Reply-To: References: Message-ID: Vojtech Juranek created ARQ-2072: ------------------------------------ Summary: Tomcat fails to start if cataliBase is not set Key: ARQ-2072 URL: https://issues.jboss.org/browse/ARQ-2072 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Affects Versions: 1.0.0.CR8 Reporter: Vojtech Juranek If {{catalinaBase}} is not set, tomcat fails to start, as {{catalinaBase}} is set to {{null}} in {{TomcatManagedConfiguration}} constructor (being set to {{catalinaHome}} which is set to {{null}} by that time). This is unexpected behaviour and breaks backward compatibility, as with previous version setting {{catalinaHome}} was enough to start Tomcat. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 2 12:15:00 2017 From: issues at jboss.org (Vojtech Juranek (JIRA)) Date: Thu, 2 Feb 2017 12:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2072) Tomcat fails to start if cataliBase is not set In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vojtech Juranek updated ARQ-2072: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/38 > Tomcat fails to start if cataliBase is not set > ---------------------------------------------- > > Key: ARQ-2072 > URL: https://issues.jboss.org/browse/ARQ-2072 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.0.CR8 > Reporter: Vojtech Juranek > > If {{catalinaBase}} is not set, tomcat fails to start, as {{catalinaBase}} is set to {{null}} in {{TomcatManagedConfiguration}} constructor (being set to {{catalinaHome}} which is set to {{null}} by that time). > This is unexpected behaviour and breaks backward compatibility, as with previous version setting {{catalinaHome}} was enough to start Tomcat. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 3 08:20:00 2017 From: issues at jboss.org (Tomas David (JIRA)) Date: Fri, 3 Feb 2017 08:20:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas David updated ARQ-2060: ----------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/69 > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha1 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 3 12:49:04 2017 From: issues at jboss.org (Reza Rahman (JIRA)) Date: Fri, 3 Feb 2017 12:49:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13358559#comment-13358559 ] Reza Rahman commented on ARQ-567: --------------------------------- Please move this forward. This can help dramatically improve test performance. > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Feb 4 01:25:03 2017 From: issues at jboss.org (Felipe C. (JIRA)) Date: Sat, 4 Feb 2017 01:25:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13358670#comment-13358670 ] Felipe C. commented on ARQ-567: ------------------------------- Hello all! I agree with [~rezarahman]! I made a POC in a project at my work and some members didn't like the deploy and test time. Because of that they don't want to use Arquillian, it bothers me a lot. I did another POC on my last work using https://github.com/felipecalmeida/arquillian-suite-extension and I was sattisfied with the results and the kind of development. I don't know your schedule for the next releases, but maybe you could integrate this issue. Also some new integrations could be great also, like http://concordion.org/, it's useful to QA results. Thank's! > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Feb 4 05:46:04 2017 From: issues at jboss.org (Rafael Pestano (JIRA)) Date: Sat, 4 Feb 2017 05:46:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13358674#comment-13358674 ] Rafael Pestano commented on ARQ-567: ------------------------------------ I remember doing a small benchmark between arquillian-suite-extension vs [arquillian core suite|http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162] in *2015 (Mar)* - even made a video: https://www.youtube.com/watch?v=r5e4HvVluyc - the times were pretty similar but what caught my attention was that *arquillian core suite was pretty usable at the time (almost two years ago)* so there must be a really blocker that made the work on this great feature halt. PS: Also at my company it was also a kind of "blocker" having a deploy/undeploy cycle per test class. Fortunately there was suite extension. > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Feb 4 05:46:08 2017 From: issues at jboss.org (Rafael Pestano (JIRA)) Date: Sat, 4 Feb 2017 05:46:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13358674#comment-13358674 ] Rafael Pestano edited comment on ARQ-567 at 2/4/17 5:46 AM: ------------------------------------------------------------ I remember doing a small benchmark between arquillian-suite-extension vs [arquillian core suite|http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162] in *2015 (Mar)* - even made a video: https://www.youtube.com/watch?v=r5e4HvVluyc - the times were pretty similar but what caught my attention was that *arquillian core suite was pretty usable at the time (almost two years ago)* so there must be a really blocker that made the work on this great feature halt. PS: At my company it was also a kind of "blocker" having a deploy/undeploy cycle per test class. Fortunately there was suite extension. was (Author: kwintesencja): I remember doing a small benchmark between arquillian-suite-extension vs [arquillian core suite|http://discuss.arquillian.org/t/arquillian-core-suite-subsuite-support/162] in *2015 (Mar)* - even made a video: https://www.youtube.com/watch?v=r5e4HvVluyc - the times were pretty similar but what caught my attention was that *arquillian core suite was pretty usable at the time (almost two years ago)* so there must be a really blocker that made the work on this great feature halt. PS: Also at my company it was also a kind of "blocker" having a deploy/undeploy cycle per test class. Fortunately there was suite extension. > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Feb 8 04:32:00 2017 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Wed, 8 Feb 2017 04:32:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2073) NPE in arquillian-container-se smoke test In-Reply-To: References: Message-ID: Tomas Remes created ARQ-2073: -------------------------------- Summary: NPE in arquillian-container-se smoke test Key: ARQ-2073 URL: https://issues.jboss.org/browse/ARQ-2073 Project: Arquillian Issue Type: Bug Affects Versions: 1.1.12.Final Reporter: Tomas Remes This looks like regression in 1.1.12.Final release. Simple {{JavaArchiveSmokeTest}} from [Arquillian container SE|https://github.com/arquillian/arquillian-container-se] fails with following stacktrace: {noformat} java.lang.NullPointerException at org.jboss.arquillian.test.spi.TestResult.flatten(TestResult.java:75) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:147) at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:330) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324) at sun.rmi.transport.Transport$1.run(Transport.java:200) at sun.rmi.transport.Transport$1.run(Transport.java:197) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:196) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Feb 8 04:59:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 8 Feb 2017 04:59:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2030) Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-2030. --------------------------------- Resolution: Out of Date > Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse > ------------------------------------------------------------------ > > Key: ARQ-2030 > URL: https://issues.jboss.org/browse/ARQ-2030 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tom?? Turek > Assignee: Thomas Diesler > Priority: Minor > > [Commit|https://github.com/arquillian/arquillian-container-osgi/commit/31157c2be1600929d47e79b7f4a15bc7b89f9bbd] which upgrade Karaf to version 4.0.4 for managed broke compatibility with JBoss Fuse 6.x. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:00:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:00:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1695) Integrate Spacelift into Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1695. ------------------------------- > Integrate Spacelift into Drone > ------------------------------ > > Key: ARQ-1695 > URL: https://issues.jboss.org/browse/ARQ-1695 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > > Spacelift can be used for following tasks: > * Download and execution of Selenium Server > * Download of ChromeDriver binary > * Download of IEDriver binary (optional, might not be needed as of IE11+) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:01:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:01:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2060: -------------------------------- Fix Version/s: (was: drone_2.1.0.Alpha1) > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:01:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:01:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2060: -------------------------------- Fix Version/s: drone_2.1.0.Alpha2 > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:03:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2062. ------------------------------- Resolution: Done Landed in https://github.com/arquillian/arquillian-extension-drone/commit/db1f9e339b25893e97fefccbb833a9a6049c0e4d > Upgrade jboss-parent to latest version (21) > ------------------------------------------- > > Key: ARQ-2062 > URL: https://issues.jboss.org/browse/ARQ-2062 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:03:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2063) Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2063. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/250f206b1a0529190baa1264baad736c8f0c5aee > Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 > ------------------------------------------------------------ > > Key: ARQ-2063 > URL: https://issues.jboss.org/browse/ARQ-2063 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:04:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:04:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2064) Upgrade JUnit to 4.12 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2064. ------------------------------- Resolution: Done pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/08fdb83b5882baddec4d110b0916fb61d3ef276a > Upgrade JUnit to 4.12 > --------------------- > > Key: ARQ-2064 > URL: https://issues.jboss.org/browse/ARQ-2064 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:06:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:06:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1826) Download Explorer binary for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1826: -------------------------------- Fix Version/s: drone_2.1.0.Alpha1 (was: drone_2.1.0.Final) > Download Explorer binary for Drone > ---------------------------------- > > Key: ARQ-1826 > URL: https://issues.jboss.org/browse/ARQ-1826 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 10 09:06:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 10 Feb 2017 09:06:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1826) Download Explorer binary for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1826. ------------------------------- > Download Explorer binary for Drone > ---------------------------------- > > Key: ARQ-1826 > URL: https://issues.jboss.org/browse/ARQ-1826 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Feb 14 10:18:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 14 Feb 2017 10:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1652) Cannot auto install arquillian-bundle on windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1652. --------------------------------- Resolution: Out of Date > Cannot auto install arquillian-bundle on windows > ------------------------------------------------ > > Key: ARQ-1652 > URL: https://issues.jboss.org/browse/ARQ-1652 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Thomas Diesler > Fix For: osgi_2.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Feb 14 10:18:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 14 Feb 2017 10:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1619) Tomcat managed container ignores allowConnectingToRunningServer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1619. --------------------------------- Resolution: Out of Date > Tomcat managed container ignores allowConnectingToRunningServer > --------------------------------------------------------------- > > Key: ARQ-1619 > URL: https://issues.jboss.org/browse/ARQ-1619 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The flag is not checked > {code} > if(manager.isRunning()) > { > throw new LifecycleException( > "The server is already running! " + > "Managed containers does not support connecting to running server instances due to the " + > "possible harmful effect of connecting to the wrong server. Please stop server before running or " + > "change to another type of container.\n" + > "To disable this check and allow Arquillian to connect to a running server, " + > "set allowConnectingToRunningServer to true in the container configuration" > ); > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Feb 14 10:18:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 14 Feb 2017 10:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1649) FrameworkMBean.installBundle() uses URL to local maven repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1649. --------------------------------- Resolution: Out of Date > FrameworkMBean.installBundle() uses URL to local maven repo > ----------------------------------------------------------- > > Key: ARQ-1649 > URL: https://issues.jboss.org/browse/ARQ-1649 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Thomas Diesler > Fix For: osgi_2.0.0.Final > > > Auto install of the arquillian-bundle may fail on remote target containers. The target container is given an URL to the arquillian-bundle that may point to the client's local maven repo -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Feb 14 10:18:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 14 Feb 2017 10:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1886) Support remote containers on remote hosts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1886. --------------------------------- Resolution: Out of Date > 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 > > 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 (v7.2.3#72005) From issues at jboss.org Wed Feb 15 02:33:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 15 Feb 2017 02:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2074) Check if binary is already executable before trying to chmod it regardless In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2074: ----------------------------------- Summary: Check if binary is already executable before trying to chmod it regardless Key: ARQ-2074 URL: https://issues.jboss.org/browse/ARQ-2074 Project: Arquillian Issue Type: Enhancement Components: Extension - Drone Affects Versions: drone_2.1.0.Alpha1 Reporter: Matous Jobanek Assignee: Matous Jobanek https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/binary/handler/AbstractBinaryHandler.java#L201-L210 Add check if the binary is already executable -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Feb 15 05:44:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 15 Feb 2017 05:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2073) NPE in arquillian-container-se smoke test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2073. ------------------------------- Assignee: Matous Jobanek Resolution: Won't Fix The cause of the problem is in the arquillian-container-se. The class [TestDeploymentPackager merges|https://github.com/arquillian/arquillian-container-se/blob/e1d6368a6b7adfb5bf9cb7a9262339b8112728c6/container-se-managed/src/main/java/org/jboss/arquillian/container/se/managed/jmx/TestDeploymentPackager.java#L41] all auxiliary archives into one Java archive, which means that there will be only one service provider of the service: {{org.jboss.arquillian.container.test.spi.RemoteLoadableExtension}} As a result of this state is that only one remote extension is loaded and the test results cannot be properly set. I'm closing this issue as it is not a bug in Arquillian. > NPE in arquillian-container-se smoke test > ----------------------------------------- > > Key: ARQ-2073 > URL: https://issues.jboss.org/browse/ARQ-2073 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Tomas Remes > Assignee: Matous Jobanek > > This looks like regression in 1.1.12.Final release. Simple {{JavaArchiveSmokeTest}} from [Arquillian container SE|https://github.com/arquillian/arquillian-container-se] fails with following stacktrace: > {noformat} > java.lang.NullPointerException > at org.jboss.arquillian.test.spi.TestResult.flatten(TestResult.java:75) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:147) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:330) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) > at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) > at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) > at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) > at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324) > at sun.rmi.transport.Transport$1.run(Transport.java:200) > at sun.rmi.transport.Transport$1.run(Transport.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Feb 15 05:47:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 15 Feb 2017 05:47:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2075) In debug mode print information about loaded extensions In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2075: ----------------------------------- Summary: In debug mode print information about loaded extensions Key: ARQ-2075 URL: https://issues.jboss.org/browse/ARQ-2075 Project: Arquillian Issue Type: Enhancement Components: core Affects Versions: 1.1.12.Final Reporter: Matous Jobanek When the test is run with a property arquillian.debug then there should be printed a list of all loaded extensions on the stdout. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Feb 15 06:00:00 2017 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Wed, 15 Feb 2017 06:00:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2073) NPE in arquillian-container-se smoke test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13363732#comment-13363732 ] Tomas Remes commented on ARQ-2073: ---------------------------------- [~mjobanek] Thanks for analysis. It's already fixed in Arquillian Container SE. > NPE in arquillian-container-se smoke test > ----------------------------------------- > > Key: ARQ-2073 > URL: https://issues.jboss.org/browse/ARQ-2073 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Tomas Remes > Assignee: Matous Jobanek > > This looks like regression in 1.1.12.Final release. Simple {{JavaArchiveSmokeTest}} from [Arquillian container SE|https://github.com/arquillian/arquillian-container-se] fails with following stacktrace: > {noformat} > java.lang.NullPointerException > at org.jboss.arquillian.test.spi.TestResult.flatten(TestResult.java:75) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:147) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:330) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) > at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) > at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) > at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) > at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324) > at sun.rmi.transport.Transport$1.run(Transport.java:200) > at sun.rmi.transport.Transport$1.run(Transport.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 04:41:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 16 Feb 2017 04:41:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2071) Use save function for checking if tomcat is running In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2071. ------------------------------- Fix Version/s: tomcat_1.0.0.CR10 Assignee: Vojtech Juranek Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/67bf420546ce4959cbc10237af5a38505340a34c > Use save function for checking if tomcat is running > --------------------------------------------------- > > Key: ARQ-2071 > URL: https://issues.jboss.org/browse/ARQ-2071 > Project: Arquillian > Issue Type: Enhancement > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR8 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: tomcat_1.0.0.CR10 > > > Currently AQR use {{list}} method of tomcat manager to find out if container is running. However, some session manager may not support this operation (e.g. because of security reasons or other). In such case ARQ fails to start tomcat. It would be nice to use some more safe method, which will be very likely implemented everwhere, e.g. {{serverinfo}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 04:50:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 16 Feb 2017 04:50:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2072) Tomcat fails to start if cataliBase is not set In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2072. ------------------------------- Fix Version/s: tomcat_1.0.0.CR10 Assignee: Vojtech Juranek Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/be1d69638f574c6fa380518e7b54a74e400f5e8e > Tomcat fails to start if cataliBase is not set > ---------------------------------------------- > > Key: ARQ-2072 > URL: https://issues.jboss.org/browse/ARQ-2072 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.0.CR8 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: tomcat_1.0.0.CR10 > > > If {{catalinaBase}} is not set, tomcat fails to start, as {{catalinaBase}} is set to {{null}} in {{TomcatManagedConfiguration}} constructor (being set to {{catalinaHome}} which is set to {{null}} by that time). > This is unexpected behaviour and breaks backward compatibility, as with previous version setting {{catalinaHome}} was enough to start Tomcat. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 08:31:01 2017 From: issues at jboss.org (Tomas David (JIRA)) Date: Thu, 16 Feb 2017 08:31:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas David updated ARQ-2060: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:48:01 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:48:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2076) Test Linking 1 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2076: ---------------------------------- Summary: Test Linking 1 Key: ARQ-2076 URL: https://issues.jboss.org/browse/ARQ-2076 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:48:01 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:48:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2077) Test Linking 2 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2077: ---------------------------------- Summary: Test Linking 2 Key: ARQ-2077 URL: https://issues.jboss.org/browse/ARQ-2077 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:49:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:49:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2076) Test Linking 1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen deleted ARQ-2076: ------------------------------- > Test Linking 1 > -------------- > > Key: ARQ-2076 > URL: https://issues.jboss.org/browse/ARQ-2076 > Project: Arquillian > Issue Type: Feature Request > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:49:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:49:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2077) Test Linking 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen deleted ARQ-2077: ------------------------------- > Test Linking 2 > -------------- > > Key: ARQ-2077 > URL: https://issues.jboss.org/browse/ARQ-2077 > Project: Arquillian > Issue Type: Feature Request > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:55:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2079) Test Linking 2 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2079: ---------------------------------- Summary: Test Linking 2 Key: ARQ-2079 URL: https://issues.jboss.org/browse/ARQ-2079 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:55:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2078) Test Linking 1 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2078: ---------------------------------- Summary: Test Linking 1 Key: ARQ-2078 URL: https://issues.jboss.org/browse/ARQ-2078 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:56:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2078) Test Linking 1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen deleted ARQ-2078: ------------------------------- > Test Linking 1 > -------------- > > Key: ARQ-2078 > URL: https://issues.jboss.org/browse/ARQ-2078 > Project: Arquillian > Issue Type: Feature Request > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 16 09:56:00 2017 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 16 Feb 2017 09:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2079) Test Linking 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen deleted ARQ-2079: ------------------------------- > Test Linking 2 > -------------- > > Key: ARQ-2079 > URL: https://issues.jboss.org/browse/ARQ-2079 > Project: Arquillian > Issue Type: Feature Request > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 17 06:51:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 17 Feb 2017 06:51:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2080) Improper closing of browsers configured via remote webdrivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2080: -------------------------------- Issue Type: Bug (was: Enhancement) > Improper closing of browsers configured via remote webdrivers > ------------------------------------------------------------- > > Key: ARQ-2080 > URL: https://issues.jboss.org/browse/ARQ-2080 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.1.0.Alpha1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha2 > > > When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. > https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 17 06:51:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 17 Feb 2017 06:51:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2080) Improper closing of browsers configured via remote webdrivers In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2080: ----------------------------------- Summary: Improper closing of browsers configured via remote webdrivers Key: ARQ-2080 URL: https://issues.jboss.org/browse/ARQ-2080 Project: Arquillian Issue Type: Enhancement Components: Extension - Drone Affects Versions: drone_2.1.0.Alpha1 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.0.Alpha2 When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 17 06:55:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 17 Feb 2017 06:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2080) Improper closing of browsers configured via remote webdrivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2080: -------------------------------- Description: When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 Steps to reproduce: run ReusableRemoteWebDriverTestCase with visible browser (eg. firefox) was: When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 > Improper closing of browsers configured via remote webdrivers > ------------------------------------------------------------- > > Key: ARQ-2080 > URL: https://issues.jboss.org/browse/ARQ-2080 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.1.0.Alpha1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha2 > > > When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. > https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 > Steps to reproduce: run ReusableRemoteWebDriverTestCase with visible browser (eg. firefox) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Feb 17 10:41:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 17 Feb 2017 10:41:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2080) Improper closing of browsers configured via remote webdrivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2080: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/75 > Improper closing of browsers configured via remote webdrivers > ------------------------------------------------------------- > > Key: ARQ-2080 > URL: https://issues.jboss.org/browse/ARQ-2080 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.1.0.Alpha1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha2 > > > When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed. > https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187 > Steps to reproduce: run ReusableRemoteWebDriverTestCase with visible browser (eg. firefox) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Feb 23 02:32:00 2017 From: issues at jboss.org (Ankit Choudhary (JIRA)) Date: Thu, 23 Feb 2017 02:32:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-553) NullPointerException in arquillianBeforeClass when running with testng in parallel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13367874#comment-13367874 ] Ankit Choudhary commented on ARQ-553: ------------------------------------- Is there any workaround for above problem. Arquillian dependency i m using are: org.jboss.arquillian.testng arquillian-testng-standalone 1.1.11.Final org.jboss.arquillian.graphene graphene-webdriver-impl 2.1.0.Final org.jboss.arquillian.extension arquillian-drone-webdriver 2.0.1.Final > NullPointerException in arquillianBeforeClass when running with testng in parallel > ---------------------------------------------------------------------------------- > > Key: ARQ-553 > URL: https://issues.jboss.org/browse/ARQ-553 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.0.0.CR1, 1.0.0.CR2 > Reporter: Tom Hintz > Priority: Critical > > Running with testng in parallel causes a NPE in org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:76), even with one thread. > testng runs arquillianBeforeSuite on main, but arquillianBeforeClass on pool-2-thread-1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)