[wildfly-dev] Is JMX Needed in Core?

[Brian Stansberry]

IMHO wildfly-system-jmx does not need to be in core. It's analogous to 
wildfly-pojo and that's not in core.

We should sort out the wildfly-server dependency, whatever it is, and 
either eliminate it or make it something that relies on an optional 
capability.

On 7/9/14, 6:52 AM, Tomaž Cerar wrote:
> Unfortunately it is needed.
>
> At least at this point of the project.
> I tired hard not to have it back when I was doing just separate core build.
>
> Current dependency tree for it includes:
>
> - wildfly-server
> - wildfly-system-jmx
>
> + arquillian, but that is not a problem anymore given that we moved it
> out of core and it is not required anymore.
>
> But probably we can revisit that and try to remove it now that there is
> no need for arq anymore in core.
> Big chunk of core testsuite will need to be updated to not use jmx
> subsystem anymore.
>
>
> Darren, can you create jira for this and assign it to me? I will take look.
>
> --
> tomaz
>
>
>
> On Wed, Jul 9, 2014 at 12:47 PM, Darran Lofthouse
> <darran.lofthouse at jboss.com <mailto:darran.lofthouse at jboss.com>> wrote:
>
>     Working with the split repo just questioning if JMX is really needed in
>     core?
>
>     Whilst most distributions would include it I am not convinced it is a
>     subsystem all must have.
>
>     Regards,
>     Darran Lofthouse.
>     _______________________________________________
>     wildfly-dev mailing list
>     wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


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