-
Bug
-
Resolution: Done
-
Major
-
7.1.1.CR2
-
None
This is a follow up to JBEAP-13094.
Having a deployment with jboss-deployment-structure like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <module name="deployment.application-exception-api"> <resources> <resource-root path="application-exception-api.jar"/> </resources> <dependencies> <module name="javax.ejb.api" export="true"/> <module name="javaee.api" export="true"/> <module name="javax.api" export="true"/> </dependencies> <module-alias name="deployment.api" /> </module> <sub-deployment name="application-exception-ejb.jar"> <dependencies> <module name="deployment.api" annotations="true" meta-inf="export"/> </dependencies> </sub-deployment> </jboss-deployment-structure>
it fails to parse.
- clones
-
WFCORE-3670 module defined with an alias in jboss-deployment-structure.xml with fails to parse when annotations=true
- Closed
- is incorporated by
-
JBEAP-17223 [GSS](7.2.z) Upgrade WildFly Core from 6.0.15 to 6.0.16
- Closed
- is related to
-
JBEAP-16712 [GSS](7.2.z) WFCORE-4475 - jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module
- Closed
-
JBEAP-17378 [QA](7.2.z) Integration Test for JBEAP-14310
- Closed
- relates to
-
JBEAP-13094 [GSS](7.1.z) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
- Closed