I'm starting to have doubts about this split.
Right now I'm trying to integrate the Keycloak (client-side) adapter
into build-core so that the web console can use Keycloak for
authentication. The problem is that there is a huge web of dependencies
that must be moved over from build to build-core.
What exactly is the split trying to solve?
On 6/27/2014 12:19 PM, Stuart Douglas wrote:
> Hi all,
> So I am moderately confident that we will be ready to split out Wildfly
> core into a separate repository early next week (I'm not saying that it
> will definitely happen in this time frame, just that it should be possible).
> Once this is ready to go I think the basic process will be:
> - Code freeze on Master
> - Create the core repo, push new rewritten core history
> - Release core 1.0.0.Beta1
> - Create PR against core WF repo that deletes everything in core, and
> uses the core 1.0.0.Beta1 release
> - End of code freeze
> wildfly-dev mailing list
wildfly-dev mailing list