[wildfly-dev] Is JMX Needed in Core?

[Brian Stansberry]

On 7/9/14, 6:00 PM, Tomaž Cerar wrote:
>
> On Wed, Jul 9, 2014 at 9:35 PM, Brian Stansberry
> <brian.stansberry at redhat.com <mailto:brian.stansberry at redhat.com>> wrote:
>
>
>     Does logging belong in web then then? Still seems like something that
>     even the uber-minimalists would want. I ask because it bugs me that we
>     have two meanings now for "core" -- the old "core" notion that was the
>     true core with zero subsystems, and now this new wildfly-core dist,
>     which has subsystems.
>
>
> Core *current* comes with following subsystems:
> - logging
> - jmx (on the way out)
> - deployment-scanner
> - remoting
> - io (because of remoting)
>
> I agree that jmx needs to go out,
> deployment scanner needs to stay.
> And remoting is needed to make cli & alike work...
>

Remoting and io libs are needed, but not the subsystems themselves.

But, we've discussed some having the current <management> stuff becoming 
subsystems once we have proper HC extensions/subsystems, so at that 
point there *will be* subsystems needed for core.

Seems my concern about two meanings of "core" won't matter at that point 
anyway.

Thanks.


-- 
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat