-
Task
-
Resolution: Done
-
Blocker
-
None
The module for the extension should still be provisioned to enable parsing existing configurations.
- blocks
-
-
- Open
-
[WFLY-19212] Remove the Security Manager extension from WildFly Preview default configuration.
Darran Lofthouse
added a comment - bstansbe@redhat.com On this one I was actually thinking more about excluding it by default from the feature pack used to provision WildFly Preview or Jakarta EE 11 - I am not sure what a model only variant would give us.
Darran Lofthouse
added a comment - bstansbe@redhat.com On this one I was actually thinking more about excluding it by default from the feature pack used to provision WildFly Preview or Jakarta EE 11 - I am not sure what a model only variant would give us. 
Brian Stansberry
added a comment - darran.lofthouse@redhat.com I think this should be about integrating a model-only variant of it. That's what we are going to have to do in standard WF and doing it differently in WFP doesn't gain anything and increases the overall amount of effort.
Brian Stansberry
added a comment - darran.lofthouse@redhat.com I think this should be about integrating a model-only variant of it. That's what we are going to have to do in standard WF and doing it differently in WFP doesn't gain anything and increases the overall amount of effort. 
From some other discussion I think I see more, I plan to continue to use this issue to work on the removal from the default configuration aspect, I have then created https://issues.redhat.com/browse/WFLY-20213 which would be the no-op subsystem with migrate ops for migrating existing configurations.