-
Enhancement
-
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.
An EAPDOC should follow up to document this change in the EAP Migration Guide.
- account is impacted by
-
EAPDOC-2781 Review the wildfly-elytron dependency referenced by our end-user BOMs
-
- Closed
-
- clones
-
WFLY-18097 Review the wildfly-elytron dependency referenced by our end-user BOMs
-
- Resolved
-
- incorporates
-
JBEAP-30648 jboss-eap-ee BOM is using upstream version of wildfly-elytron
-
- Verified
-