Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Description
The module spec for any module created by ExternalModuleSpecService has a dependency on javaee.api added. That should be an optional dependency, allowing this feature to be used in slimmed servers that may not have the javaee.api module installed.
It seems it's pretty easy to provision such a server, as that module is not heavily depended on:
$ git grep javaee.api | grep module.xml | grep -v src/test feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml: <module name="javaee.api"/> feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml: reexported by javaee.api. --> feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml:<module xmlns="urn:jboss:module:1.5" name="javaee.api"> feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml: <module name="javaee.api"/> jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml: <module name="javaee.api"/> jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml: reexported by javaee.api. --> jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml: <module name="javaee.api"/> jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml: reexported by javaee.api. -->
JavaEEDependencyProcessor in WildFly explicitly does not add javaee.api as a dep.
