[jboss-jira] [JBoss JIRA] (WFLY-4552) Allow specify system packages for Arquillian Wildfly adaptor

Ondřej Chaloupka created WFLY-4552: -------------------------------------- Summary: Allow specify system packages for Arquillian Wildfly adaptor Key: WFLY-4552 URL: https://issues.jboss.org/browse/WFLY-4552 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondřej Chaloupka Currently there is no way how to specify module system packages when WildFly is started via Arquillian as managed container started manually. Currently there is default value {{-Djboss.modules.system.pkgs=org.jboss.byteman}} which overrides any value which is specified in {{JAVA_OPTS}} I use method {{org.jboss.arquillian.container.test.api.ContainerController.start(String containerQualifier, Map<String, String> config)}} In JBoss AS7 I've added the parameter {{-Djboss.modules.system.pkgs}} as part of {{JAVA_OPTS}} property and such property was passed to starting container and everything worked fine. Starting of WildFly defines its own default parameter which overrides value defined in {{JAVA_OPTS}} env variable. The startup configuration adds it's own property defined as {{-Djboss.modules.system.pkgs=org.jboss.byteman}} which override my definition. I've quickly checked the code and startInternal method https://github.com/wildfly/wildfly-arquillian/blob/master/container-manag... builds the command where method {{getSystemPackages()}} defines the modules sytem packages https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... but the {{ManagedDeployableContainer}} does not give any possibility to set configuration option of modules system packages with method {{StandaloneCommandBuilder.addSystemPackage}} or {{StandaloneCommandBuilder.setSystemPackages}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)