At some point (unless Jason agrees core does not need the subsystem) we
are going to be looking to move the Elytron subsystem over from it's
isolated repository into the wildfly-core repository, to make that
process less painful and also to start giving other teams more
confidence in it's stability I was thinking if we should start reviewing
the subsystem early.
This isn't a call for everyone to check out the whole subsystem and
comment on it all as we know there are some resources in there still to
However on the Elytron team we know which pieces are stable / reaching
stability so I was thinking if we were to start grouping related
resource maybe by capability we could set up some smaller reviews.
Ideally then when I submit the PR to merge into wildfly-core the actual
content of the subsystem should be reviewed already and the review of
that PR should be more about how it is fitting into the wildfly-core
maven project structure.
If others are interested in this I will see how we can start to chop it
into review-able chunks.
>> On Jun 6, 2016, at 7:13 AM, Darran Lofthouse <[hidden email]> wrote:
>> At some point (unless Jason agrees core does not need the subsystem)
> Did someone make that argument?
> It seems to me it has to be in core because it replaces security realms?
As it stands today the Elytron subsystem is optional until the point
where you release a distribution that you want to secure using it.
So core contains the Elytron module and references items from the
Elytron subsystem as capabilities.
The legacy security realms are going to be staying around for a while
allowing either new or old to be used.
WildFly on the other hand could pull in the Elytron subsystem and
contain default configuration for the feature packs entirely backed by
So really do we have a requirement at the moment to release a
distribution based on core? From what I hear many other distributions
still slim WildFly rather than add to core.