Brian Stansberry created AS7-3880: ------------------------------------- Summary: AS7-2824 fix removes ability to specify multiple paths in ARQ modulePath config Key: AS7-3880 URL: https://issues.jboss.org/browse/AS7-3880 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Reporter: Brian Stansberry Assignee: Thomas Diesler Fix For: 7.1.1.Final The AS7-2824 fix at https://github.com/jbossas/jboss-as/commit/cdb3b1d8f9453b1eb4ec617a83509b... adds a contract to ManagedDeployableContainer such that the ARQ config modulesPath must be a single file and must point to a directory with a sibling named "bundles". Neither seem like valid constraints for any Arquillian user who isn't interested in OSGi. See Galder's comment on AS7-2824 for how this breaks his usage. I think the issue here was identifying which of many dirs to use as jboss.modules.dir, which if not set to a valid location will result in failure to start the OSGi subsystem? Perhaps some logic to give preference to $JBOSS_HOME/modules if that is one of the items in the modulesPath list? Failing that, use the first item and document that? For the jboss.bundles.dir property, check for a sibling to jboss.modules.dir, if not found check for a sibling to any of the other items in the modulesPath list, if not found use $JBOSS_HOME/bundles? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira