6:31 a.m.
[
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
4099
days inactive
4099
days old
arquillian-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
David Mann (JIRA)