<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 6/30/2014 6:15 PM, Tomaž Cerar
wrote:<br>
</div>
<blockquote
cite="mid:CAMquZP6up9c5udO2RHBkDFUfcsLP=WaUpUvWdc2cUkbaDUqO7Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Stan,<br>
<br>
</div>
what problems do you have?<br>
Last time I was looking into your integration code, you didn't
have any deps that didn't exist in core.<br>
</div>
</div>
</blockquote>
The Keycloak adapter relies on jackson, RestEasy, iharder,
httpcomponents, and undertow-servlet. I was able to get rid of
undertow-servlet, but the others end up pulling in a ton of stuff.<br>
<blockquote
cite="mid:CAMquZP6up9c5udO2RHBkDFUfcsLP=WaUpUvWdc2cUkbaDUqO7Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
--<br>
</div>
tomaz<br>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Mon, Jun 30, 2014 at 11:47 PM, Stan
Silvert <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
<span class="HOEnZb"><font color="#888888"><br>
Stan<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><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 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 moz-do-not-send="true"
href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
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>
</blockquote>
<br>
</body>
</html>