On 6/30/2014 6:15 PM, Tomaž Cerar wrote:
Stan,
what problems do you have?
Last time I was looking into your integration code, you didn't have
any deps that didn't exist in core.
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.
--
tomaz
On Mon, Jun 30, 2014 at 11:47 PM, Stan Silvert <ssilvert(a)redhat.com
<mailto:ssilvert@redhat.com>> 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 <mailto:wildfly-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev