-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
Undefined
-
---
-
---
By doing this we will have a much better record of which areas of WildFly Elytron are used by which components in the application server.
We should be cautious to avoid any transitive dependencies.
This task is only to look at the Maven dependencies, the modules should also be looked at later if we decide it is appropriate.
- blocks
-
WFCORE-5374 Remove the wildfly-elytron dependency from the main pom.xml file
- Pull Request Sent
- clones
-
WFCORE-5263 Update all projects with a dependency on wildfly-elytron to use individual modules.
- Closed
- is blocked by
-
WEJBHTTP-60 Update project with a dependency on wildfly-elytron to use individual modules
- Resolved
-
WFNC-64 Update project with a dependency on wildfly-elytron to use individual modules
- Resolved
- is cloned by
-
WFLY-11540 Update Maven dependencies to reference individual Elytron modules.
- Closed
- is related to
-
WFLY-15391 Update observability module with a dependency on wildfly-elytron to use individual modules
- Closed
- relates to
-
REM3-394 JBoss Remoting must not depend on org.wildfly.security:wildfly-elytron
- Closed