Re: [wildfly-dev] Pending core split

It really sounds like this should not be part of core, but should be something extra that just integrates with the core.

In all honesty we are highly unlikely to ever have accepted a PR that added all these dependencies to the core in any case, so it is a problem that would have had to be solved at some point anyway. Stuart Stan Silvert wrote: > 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? > > Stan > > 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 >> >> Stuart >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev