<div dir="ltr"><div><div><div><div>I think that for start we can make it by default enablable in full distro.<br><br></div>Once this is done, and extra work is done on trimming down dependencies to go as near JDK as possible<br>
</div>it could be moved to core distro.<br><br></div>Rome was not build in a day, why would KeyCloak integration / implementation be done in just one step.<br><br></div><div>Isn't it better that we start somewhere to get it out to the people to test it as soon as possible<br>
and when it is ready we decide where it is best resting place and how to get there.</div><div></div><br><div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 3, 2014 at 11:19 AM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
> The central question is, do we want Keycloak to work out of the box?<br>
> Before this issue was known, everyone answered "yes".<br>
<br>
</div>I think here we had reached the point we were answering the question "do<br>
we want it enableable out of the box?" and the answer to that was "yes"<br>
<br>
What has not been defined since the split started is what "out of the<br>
box" actually means now, are we talking out of the box for the core or<br>
out of the box for a complete assembled server?<br>
<div class="HOEnZb"><div class="h5"><br>
On 01/07/14 12:55, Stan Silvert wrote:<br>
> On 6/30/2014 10:43 PM, Stuart Douglas wrote:<br>
>> It really sounds like this should not be part of core, but should be<br>
>> something extra that just integrates with the core.<br>
> That may be true, but it's not a decision that should depend on how many<br>
> modules must be added.<br>
><br>
> The central question is, do we want Keycloak to work out of the box?<br>
> Before this issue was known, everyone answered "yes".<br>
><br>
> Should we really determine our feature set based on how many modules it<br>
> requires? I don't think we want do that, which is why I'm having<br>
> doubts about the current approach.<br>
><br>
>><br>
>> In all honesty we are highly unlikely to ever have accepted a PR that<br>
>> added all these dependencies to the core in any case, so it is a<br>
>> problem that would have had to be solved at some point anyway.<br>
>><br>
>> Stuart<br>
>><br>
>> Stan Silvert wrote:<br>
>>> I'm starting to have doubts about this split.<br>
>>><br>
>>> Right now I'm trying to integrate the Keycloak (client-side) adapter<br>
>>> into build-core so that the web console can use Keycloak for<br>
>>> authentication. The problem is that there is a huge web of dependencies<br>
>>> that must be moved over from build to build-core.<br>
>>><br>
>>> What exactly is the split trying to solve?<br>
>>><br>
>>> Stan<br>
>>><br>
>>> On 6/27/2014 12:19 PM, Stuart Douglas wrote:<br>
>>>> Hi all,<br>
>>>><br>
>>>> So I am moderately confident that we will be ready to split out Wildfly<br>
>>>> core into a separate repository early next week (I'm not saying that it<br>
>>>> will definitely happen in this time frame, just that it should be<br>
>>>> possible).<br>
>>>><br>
>>>> Once this is ready to go I think the basic process will be:<br>
>>>><br>
>>>> - Code freeze on Master<br>
>>>> - Create the core repo, push new rewritten core history<br>
>>>> - Release core 1.0.0.Beta1<br>
>>>> - Create PR against core WF repo that deletes everything in core, and<br>
>>>> uses the core 1.0.0.Beta1 release<br>
>>>> - End of code freeze<br>
>>>><br>
>>>> Stuart<br>
>>>> _______________________________________________<br>
>>>> wildfly-dev mailing list<br>
>>>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
>>><br>
>>> _______________________________________________<br>
>>> wildfly-dev mailing list<br>
>>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>