-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
The urn:jboss:deployment-structure:#.# schemas's moduleExclusionType allows configuration of both a module name and a slot, and the parsers capture both by creating a ModuleIdentifier and using that in the object created from the parsed content.
But later in processing the code calls "ModuleIdentifier.getName() and stores only that, thus throwing away the slot. And then later code when trying to see if a module should be excluded does the same.
The effect is a user cannot exclude only a particular slot.
I believe this is something I broke in WFCORE-6871 / WildFly 33 and is thus a regression. So I've converted this to 'Blocker'.
- blocks
-
WFCORE-7062 Remove all non-breaking uses of ModuleIdentifier
-
- Open
-
- is caused by
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
