-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFCORE-6755] Move the org.wildfly.security:wildfly-elytron-dynamic-ssl artifact into its own module #6066
base: main
Are you sure you want to change the base?
Conversation
Core -> Full Integration Build 13655 outcome was FAILURE using a merge of 1fc8829 |
@yersan FYI I will be working on a PR to promote this to default soon, although would be good to know we could solve this situation if it comes up again so I think still worth proceeding for now. |
@yersan are we proceeding with this one? |
@darranl I want to back to this once we have passed the feature freeze, I plan to take a closer look next week |
…sl artifact into its own module
… if we have provisioned to an stability level above community Jira issue: https://issues.redhat.com/browse/WFCORE-6755
@darranl kicked it off again, I've added |
Supersedes #5947
Jira issue: https://issues.redhat.com/browse/WFCORE-6755
See https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/topic/Layers.20and.20optional.20packages.
This PR includes #5947 but removes the community stability property configuration from
org.wildfly.security.elytron-dynamic-ssl
JBoss Modules module and adds its package as required for the Elytron layer. Until getting a better approach for this case, this will fix the issue reported by the test case where this module was not provisioned when using Elytron Galleon Layer and ensure we can usedefault
stability level out of the box when the server is built targetting this stability level.