[
https://issues.jboss.org/browse/WFCORE-2540?page=com.atlassian.jira.plugi...
]
Darran Lofthouse commented on WFCORE-2540:
------------------------------------------
[~brian.stansberry] This may be a good topic for tomorrow's call.
We don't really want JACC in Core but as the subsystem needs to manage JACC and the
subsystem needs to be in Core the dependency has been pulled in. Even more if we add
Elytron the core feature feature pack we also don't really want JACC.
Any thoughts on either how a subsystem can be slimmed to make it compatible with core, or
expanded to satisfy it's WildFly requirements.
Peter had explored detecting if required classes are available and skipping specific
resource registrations but that does not help with the XML schema.
Update JACC Version property name and version to match WildFly
--------------------------------------------------------------
Key: WFCORE-2540
URL:
https://issues.jboss.org/browse/WFCORE-2540
Project: WildFly Core
Issue Type: Component Upgrade
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 3.0.0.Beta10
(The definition in WildFly can likely be removed as well)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)