[
https://issues.jboss.org/browse/WFLY-10507?page=com.atlassian.jira.plugin...
]
Tomaz Cerar commented on WFLY-10507:
------------------------------------
wildfly-arquillian-parent was removed as it was causing issues with what versions of
components are managed.
if you import it with scope=import, it brings in also dependencies from wildfly-core such
as wildfly-controller and others that are build dependanices of arquillian adapter. As
such we did have issues in testsuite when in some rare cases the old version(as
wildfly-arquillian is always 1-2 versions behind current core release) of
wildfly-controller came on test classpath and started causing havoc.
I am not sure what exact issue was, but I think it was related to embedded stuff.
Adding back -remote as managed makes sense, but do it in a proper way, via a profile or
something like that. Just do not import parent directly.
wildfly-arquillian-container-remote not managed anymore
-------------------------------------------------------
Key: WFLY-10507
URL:
https://issues.jboss.org/browse/WFLY-10507
Project: WildFly
Issue Type: Bug
Reporter: Peter Palaga
Assignee: Kabir Khan
In WF12, {{wildfly-arquillian-container-remote}} used to be managed via importing
{{wildfly-arquillian-parent}} to {{wildfly-parent}} at [1].
This is not the case anymore. {{wildfly-arquillian-container-managed}} is the only kind
of Arquillian container managed in WF13.
I believe, {{wildfly-arquillian-container-remote}} and other kinds of Arq. containers
from {{wildfly-arquillian-parent}} should be managed somewhere in WF. My usecase is a
docker integration test in WildFly Camel code base. WF version is the only thing I know
and based on that I'd like to get a managed version of
wildfly-arquillian-container-remote.
[1]
https://github.com/wildfly/wildfly/blob/12.0.0.Final/pom.xml#L6435
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)