[
https://issues.jboss.org/browse/WFLY-10507?page=com.atlassian.jira.plugin...
]
Kabir Khan commented on WFLY-10507:
-----------------------------------
[~ctomc] When undoing the component-matrix change I followed what was in the
component-matrix pom.xml in the run-up to WF13. So, I believe that removing the arquillian
parent happened as part of your component-matrix work. Does adding the parent back in fit
with what you had in mind?
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)