Matous Jobanek created WFLY-5679: ------------------------------------ Summary: Classloading issue when running test by using both wildfly-arquillian-container-managed and jboss-as-arquillian-container-managed together Key: WFLY-5679 URL: https://issues.jboss.org/browse/WFLY-5679 Project: WildFly Issue Type: Bug Reporter: Matous Jobanek Assignee: Jason Greene When there is a test starting both containers WF9 and JBoss AS 7 (eg. for migration verification) the deployment and stopping of the containers don't behave correctly. To start both of the containers I need relevant container adapters: - {{org.jboss.as:jboss-as-arquillian-container-managed}} - {{org.wildfly.arquillian:wildfly-arquillian-container-managed (or org.wildfly:wildfly-arquillian-container-managed for WF8)}} however, in the case of the WF's adapter the packages haven't been renamed (when there was the migration from the JBoss AS to WF, even though the maven artifact had been renamed). The situation of using both of the artifacts leads to the situation that there are two Java classes with the very same name (eg. {{org.jboss.as.arquillian.container.managed.ManagedContainerExtension}}) and only one of them is used - the one that belongs to the artifact used as the first one there in the pom.xml file. So, currently there is no easy way how to run two or more containers in a combination of WF8+ and JBoss AS 7 (and older). This leads me to the main question - why the packages haven't been renamed after the migration to org.wildfly(.arquillian) ? Current situation is quite confusing and in some cases problematic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)