Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
Description
We should have a deployment processor which detects package conflicts within deployments. It should ensure that no deployment package is exported by any module provided by the application server (the ModuleSpecification#getSystemDependencies set) (excluding META-INF/** and the empty package from consideration, and maybe one or two others). The processor could either raise an error, or it could introduce a PathFilter to block the offending packages and print a warning to that effect.
We could also add other checks - like warning if the same package is present in more than one archive within the deployment that have visibility to each other, for example - but it's somewhat harder to establish hard rules about these cases that are always correct.
Attachments
Issue Links
- is related to
-
WFCORE-3522 Module dependency order for a deployment is wrong
- Open
-
WFLY-9713 Test suite tests using shrinkwrap are creating many duplicated classes
- Open