[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
by David Mann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ]
David Mann updated ARQ-1455:
----------------------------
Description:
Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/)
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
See attached test case, which can be resolved using the snippet above.
was:
Someone should add the following to the arquillian getting started tutorial
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
See attached test case,
When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
- org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
- Managed server was not started within [60] s
Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
This bug report is mainly to help people that run into the same problem.
Kind regards,
and cheers for an awesome product :-)
David
> BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
> --------------------------------------------------------------------
>
> Key: ARQ-1455
> URL: https://issues.jboss.org/browse/ARQ-1455
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: David Mann
> Attachments: arquillian-tutorial.zip
>
>
> Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/)
> <!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
> <defaultProtocol type="Servlet 3.0" />
> See attached test case, which can be resolved using the snippet above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
by David Mann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ]
David Mann updated ARQ-1455:
----------------------------
Description:
Someone should add the following to the arquillian getting started tutorial
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
See attached test case,
When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
- org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
- Managed server was not started within [60] s
Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
This bug report is mainly to help people that run into the same problem.
Kind regards,
and cheers for an awesome product :-)
David
was:
When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
- org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
- Managed server was not started within [60] s
Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
This bug report is mainly to help people that run into the same problem.
Kind regards,
and cheers for an awesome product :-)
David
> BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
> --------------------------------------------------------------------
>
> Key: ARQ-1455
> URL: https://issues.jboss.org/browse/ARQ-1455
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: David Mann
> Attachments: arquillian-tutorial.zip
>
>
> Someone should add the following to the arquillian getting started tutorial
> <!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
> <defaultProtocol type="Servlet 3.0" />
> See attached test case,
> When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
> I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
> - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
> - Managed server was not started within [60] s
> Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
> After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
> This bug report is mainly to help people that run into the same problem.
> Kind regards,
> and cheers for an awesome product :-)
> David
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
by David Mann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ]
David Mann updated ARQ-1455:
----------------------------
Component/s: Documentation
(was: Build Infrastructure)
> BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
> --------------------------------------------------------------------
>
> Key: ARQ-1455
> URL: https://issues.jboss.org/browse/ARQ-1455
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: David Mann
> Attachments: arquillian-tutorial.zip
>
>
> When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
> I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
> - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
> - Managed server was not started within [60] s
> Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
> After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
> This bug report is mainly to help people that run into the same problem.
> Kind regards,
> and cheers for an awesome product :-)
> David
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
by David Mann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ]
David Mann edited comment on ARQ-1455 at 8/15/13 7:31 AM:
----------------------------------------------------------
Ok, a few more learnings here
- We had a dependency to JBossSX in our legacy project, which lead to the error mentioned above
org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
Managed server was not started within [60] s
Turns out this was due to JBossSX pulling jboss-common 2.3 behind the scenes. Exlude it, or replace with the appropriat dependency for JBoss AS 7 (see below)
<dependency>
<groupId>jboss</groupId>
<artifactId>jbosssx</artifactId>
<version>3.2.3</version>
<exclusions>
<exclusion>
<artifactId>jboss-common</artifactId>
<groupId>jboss</groupId>
</exclusion>
</exclusions>
</dependency>
Replacing JBossSX with PicketBox does also work (why is this not in the BOMs? I have opened a feature request with them)
<dependency>
<groupId>org.picketbox</groupId>
<artifactId>picketbox</artifactId>
<version>4.0.7.Final</version>
</dependency>
- Regarding the problem at hand, everything is solved by enforcing the use of the Servlet 3.0 API for deploying. So, in arquillian.xml add
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
just before the <container qualifier= ...> element
also, it doesn't help to have the JBoss BOMs AND the Arquillian BOMs in the same pom.xml ;-)
was (Author: dxmann73):
Ok, a few more learnings here
- We had a dependency to JBossSX in our legacy project, which lead to the error mentioned above
org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
Managed server was not started within [60] s
Turns out this was due to JBossSX pulling jboss-common 2.3 behind the scenes. Exlude it, next error (see below)
<dependency>
<groupId>jboss</groupId>
<artifactId>jbosssx</artifactId>
<version>3.2.3</version>
<exclusions>
<exclusion>
<artifactId>jboss-common</artifactId>
<groupId>jboss</groupId>
</exclusion>
</exclusions>
</dependency>
Replacing JBossSX with PicketBox does also work (why is this not in the BOMs? I have opened a feature request with them)
<dependency>
<groupId>org.picketbox</groupId>
<artifactId>picketbox</artifactId>
<version>4.0.7.Final</version>
</dependency>
- Regarding the problem at hand, everything is solved by enforcing the use of the Servlet 3.0 API for deploying. So, in arquillian.xml add
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
just before the <container qualifier= ...> element
also, it doesn't help to have the JBoss BOMs AND the Arquillian BOMs in the same pom.xml ;-)
> BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
> --------------------------------------------------------------------
>
> Key: ARQ-1455
> URL: https://issues.jboss.org/browse/ARQ-1455
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build Infrastructure
> Reporter: David Mann
> Attachments: arquillian-tutorial.zip
>
>
> When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
> I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
> - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
> - Managed server was not started within [60] s
> Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
> After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
> This bug report is mainly to help people that run into the same problem.
> Kind regards,
> and cheers for an awesome product :-)
> David
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
by David Mann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ]
David Mann commented on ARQ-1455:
---------------------------------
Ok, a few more learnings here
- We had a dependency to JBossSX in our legacy project, which lead to the error mentioned above
org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
Managed server was not started within [60] s
Turns out this was due to JBossSX pulling jboss-common 2.3 behind the scenes. Exlude it, next error (see below)
<dependency>
<groupId>jboss</groupId>
<artifactId>jbosssx</artifactId>
<version>3.2.3</version>
<exclusions>
<exclusion>
<artifactId>jboss-common</artifactId>
<groupId>jboss</groupId>
</exclusion>
</exclusions>
</dependency>
Replacing JBossSX with PicketBox does also work (why is this not in the BOMs? I have opened a feature request with them)
<dependency>
<groupId>org.picketbox</groupId>
<artifactId>picketbox</artifactId>
<version>4.0.7.Final</version>
</dependency>
- Regarding the problem at hand, everything is solved by enforcing the use of the Servlet 3.0 API for deploying. So, in arquillian.xml add
<!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature -->
<defaultProtocol type="Servlet 3.0" />
just before the <container qualifier= ...> element
also, it doesn't help to have the JBoss BOMs AND the Arquillian BOMs in the same pom.xml ;-)
> BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ
> --------------------------------------------------------------------
>
> Key: ARQ-1455
> URL: https://issues.jboss.org/browse/ARQ-1455
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build Infrastructure
> Reporter: David Mann
> Attachments: arquillian-tutorial.zip
>
>
> When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.
> I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with
> - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
> - Managed server was not started within [60] s
> Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.
> After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-)
> This bug report is mainly to help people that run into the same problem.
> Kind regards,
> and cheers for an awesome product :-)
> David
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1454) Arquillian doesn't work with TestNG >= 6.6
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1454?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1454.
------------------------------
Assignee: Aslak Knutsen
Resolution: Done
Fix pushed upstream at TestNG
https://github.com/cbeust/testng/commit/f05a3af7797aa441152a3e5daa1bf5660...
> Arquillian doesn't work with TestNG >= 6.6
> ------------------------------------------
>
> Key: ARQ-1454
> URL: https://issues.jboss.org/browse/ARQ-1454
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.1.Final
> Reporter: Christian Bauer
> Assignee: Aslak Knutsen
> Priority: Critical
> Attachments: foo.tar.gz
>
>
> Works with TestNG 6.5.2 but breaks with 6.6:
> {code}
> 10:27:17,634 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-4-thread-1) Failed: bar.Foo.doStuff: org.testng.TestNGException: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:252) [arquillian-service:]
> at org.testng.internal.XmlMethodSelector.setXmlClasses(XmlMethodSelector.java:263) [arquillian-service:]
> at org.testng.TestRunner.initRunInfo(TestRunner.java:378) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:230) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:205) [arquillian-service:]
> at org.testng.TestRunner.<init>(TestRunner.java:153) [arquillian-service:]
> at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:522) [arquillian-service:]
> at org.testng.SuiteRunner.init(SuiteRunner.java:157) [arquillian-service:]
> at org.testng.SuiteRunner.<init>(SuiteRunner.java:111) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1272) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1259) [arquillian-service:]
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1113) [arquillian-service:]
> at org.testng.TestNG.run(TestNG.java:1030) [arquillian-service:]
> at org.jboss.arquillian.testng.container.TestNGTestRunner.execute(TestNGTestRunner.java:53) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:]
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) [rt.jar:1.7.0_21]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) [rt.jar:1.7.0_21]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21]
> at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_21]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:245) [arquillian-service:]
> ... 34 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1454) Arquillian doesn't work with TestNG >= 6.6
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1454?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1454:
-------------------------------
Summary: Arquillian doesn't work with TestNG >= 6.6 (was: Arquillian doesn't work with TestNG 6.6)
> Arquillian doesn't work with TestNG >= 6.6
> ------------------------------------------
>
> Key: ARQ-1454
> URL: https://issues.jboss.org/browse/ARQ-1454
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.1.Final
> Reporter: Christian Bauer
> Priority: Critical
> Attachments: foo.tar.gz
>
>
> Works with TestNG 6.5.2 but breaks with 6.6:
> {code}
> 10:27:17,634 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-4-thread-1) Failed: bar.Foo.doStuff: org.testng.TestNGException: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:252) [arquillian-service:]
> at org.testng.internal.XmlMethodSelector.setXmlClasses(XmlMethodSelector.java:263) [arquillian-service:]
> at org.testng.TestRunner.initRunInfo(TestRunner.java:378) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:230) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:205) [arquillian-service:]
> at org.testng.TestRunner.<init>(TestRunner.java:153) [arquillian-service:]
> at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:522) [arquillian-service:]
> at org.testng.SuiteRunner.init(SuiteRunner.java:157) [arquillian-service:]
> at org.testng.SuiteRunner.<init>(SuiteRunner.java:111) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1272) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1259) [arquillian-service:]
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1113) [arquillian-service:]
> at org.testng.TestNG.run(TestNG.java:1030) [arquillian-service:]
> at org.jboss.arquillian.testng.container.TestNGTestRunner.execute(TestNGTestRunner.java:53) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:]
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) [rt.jar:1.7.0_21]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) [rt.jar:1.7.0_21]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21]
> at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_21]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:245) [arquillian-service:]
> ... 34 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1454) Arquillian doesn't work with TestNG 6.6
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1454?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1454:
------------------------------------
https://github.com/cbeust/testng/pull/428
> Arquillian doesn't work with TestNG 6.6
> ---------------------------------------
>
> Key: ARQ-1454
> URL: https://issues.jboss.org/browse/ARQ-1454
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.1.Final
> Reporter: Christian Bauer
> Priority: Critical
> Attachments: foo.tar.gz
>
>
> Works with TestNG 6.5.2 but breaks with 6.6:
> {code}
> 10:27:17,634 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-4-thread-1) Failed: bar.Foo.doStuff: org.testng.TestNGException: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:252) [arquillian-service:]
> at org.testng.internal.XmlMethodSelector.setXmlClasses(XmlMethodSelector.java:263) [arquillian-service:]
> at org.testng.TestRunner.initRunInfo(TestRunner.java:378) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:230) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:205) [arquillian-service:]
> at org.testng.TestRunner.<init>(TestRunner.java:153) [arquillian-service:]
> at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:522) [arquillian-service:]
> at org.testng.SuiteRunner.init(SuiteRunner.java:157) [arquillian-service:]
> at org.testng.SuiteRunner.<init>(SuiteRunner.java:111) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1272) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1259) [arquillian-service:]
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1113) [arquillian-service:]
> at org.testng.TestNG.run(TestNG.java:1030) [arquillian-service:]
> at org.jboss.arquillian.testng.container.TestNGTestRunner.execute(TestNGTestRunner.java:53) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:]
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) [rt.jar:1.7.0_21]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) [rt.jar:1.7.0_21]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21]
> at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_21]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:245) [arquillian-service:]
> ... 34 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (ARQ-1454) Arquillian doesn't work with TestNG 6.6
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1454?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen edited comment on ARQ-1454 at 8/14/13 9:52 AM:
-------------------------------------------------------------
Aa, right. No that's not setting the protocol to be use. That's only to configure it when it's in use.
You define which to use either via the defaultProtocol element in arquillian.xml or @OverProtocol annotation on the @Deployment method.
was (Author: aslak):
Aa, right. No that's not setting the protocol to be use. That's only to configure it when it's in use.
> Arquillian doesn't work with TestNG 6.6
> ---------------------------------------
>
> Key: ARQ-1454
> URL: https://issues.jboss.org/browse/ARQ-1454
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.1.Final
> Reporter: Christian Bauer
> Priority: Critical
> Attachments: foo.tar.gz
>
>
> Works with TestNG 6.5.2 but breaks with 6.6:
> {code}
> 10:27:17,634 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-4-thread-1) Failed: bar.Foo.doStuff: org.testng.TestNGException: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:252) [arquillian-service:]
> at org.testng.internal.XmlMethodSelector.setXmlClasses(XmlMethodSelector.java:263) [arquillian-service:]
> at org.testng.TestRunner.initRunInfo(TestRunner.java:378) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:230) [arquillian-service:]
> at org.testng.TestRunner.init(TestRunner.java:205) [arquillian-service:]
> at org.testng.TestRunner.<init>(TestRunner.java:153) [arquillian-service:]
> at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:522) [arquillian-service:]
> at org.testng.SuiteRunner.init(SuiteRunner.java:157) [arquillian-service:]
> at org.testng.SuiteRunner.<init>(SuiteRunner.java:111) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1272) [arquillian-service:]
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1259) [arquillian-service:]
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1113) [arquillian-service:]
> at org.testng.TestNG.run(TestNG.java:1030) [arquillian-service:]
> at org.jboss.arquillian.testng.container.TestNGTestRunner.execute(TestNGTestRunner.java:53) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) [arquillian-service:]
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:]
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) [rt.jar:1.7.0_21]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_21]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) [rt.jar:1.7.0_21]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.ClassNotFoundException: bar.Foo from [Module "deployment.arquillian-service:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21]
> at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_21]
> at org.testng.internal.XmlMethodSelector.checkMethod(XmlMethodSelector.java:245) [arquillian-service:]
> ... 34 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months