-
Task
-
Resolution: Done
-
Major
-
None
-
None
Our end user BOMs currently reference the Elytron shaded JAR:
<dependency>
<groupId>org.wildfly.security</groupId>
<artifactId>wildfly-elytron</artifactId>
</dependency>
Should Elytron itself have a couple of use case specific BOMs with transitive dependencies on Elytron modules only so application developers could depend on one artifact and get the set needed for a specific task?
To start with, it might make sense to create a BOM with everything needed so the shaded JAR doesn't need to be referenced anymore.
- blocks
-
WFCORE-7268 We should remove wildfly-elytron managed dependency
-
- Open
-
- is blocked by
-
ELY-2915 Add a new org.wildfly.security:wildfly-elytron-all bom
-
- Pull Request Sent
-
- is cloned by
-
JBEAP-30094 Review the wildfly-elytron dependency referenced by our end-user BOMs
-
- Verified
-
- relates to
-
-
- Open
-
-
-
- Resolved
-
