[
https://issues.jboss.org/browse/AS7-3880?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3880:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
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.2.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