On 7/1/14, 7:55 AM, Brian Stansberry wrote:
On 6/30/14, 6:27 PM, Stan Silvert wrote:
> On 6/30/2014 6:03 PM, Jason Greene wrote:
>> The point of the core platform is to evolve the base manageable runtime
independent of the traditional application server. This allows for many different
frameworks and server runtimes to be based on WildFly. It’s a very real request we have
had for a long time.
>> The core platform has had a goal from the very beginning to have minimal deps, so
if you find yourself adding deps, then it either needs an alternative solution, or it
doesn’t belong in core.
> I spent most of last week trying out alternatives and teasing out
> dependencies. No joy so far.
> What if we moved domain-http into web-build? That would mean that the
> web console would not be available in core-build, but I'm not sure it
> makes sense to be there anyway. Does web console even run against
The http interface is a core capability, even if there is no console.
There are other clients. JON plus whatever custom stuff people have
added over the years.
The console itself is not included in the core. Mostly due to size
considerations -- we want the core to be very light.
What specific issues are you seeing?
Never mind this last question -- I replied before getting all my mail
and didn't see the rest of the thread.
>> On Jun 30, 2014, at 4:47 PM, Stan Silvert <ssilvert(a)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?
>>> 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
>>>> will definitely happen in this time frame, just that it should be
>>>> 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
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
> wildfly-dev mailing list
Senior Principal Software Engineer
JBoss by Red Hat