I think this is an interesting idea. I have a couple questions though...
Is the idea to separate the code from the WildFly branding? Is the
recent modularization effort of Elytron not sufficient to make the
subprojects consumable by downstream projects, or are there dependency
issues that are coming into play, or some other motivating factor?
SmallRye Common hasn't quite gotten to the "wheels hitting the road"
point (just due to backlog/resourcing) so there might be some delay in
releasing these bits/making them live, so that might be something to
consider if there is a schedule in play here. Also I'm wary of
blowing it up too quickly considering its low (effectively negative)
That said I think it's reasonable to move things there if they're
sufficiently "neutral", especially things that already had a home in
WildFly Common previously, assuming they weren't too regrettable
implementation-wise. :-) The others we'd probably want to evaluate on
a case-by-case basis, probably in dependency order if it comes to
that, to ensure that we're really not making it "Common and Also Some
Security" for example. Some of these things might be better done as
top-level SmallRye projects, or part of a bigger effort to make
Elytron more of a SmallRye thing in general, or whatever.
> You received this message because you are subscribed to the Google Groups "SmallRye" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to smallrye+u...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/smallrye/d459b6cf-f4a8-4199-8bab-e64d7d26799c%40googlegroups.com