<div dir="ltr"><div><div><div><div><div><div><div><div>Unfortunately it is needed. <br><br></div>At least at this point of the project. <br>I tired hard not to have it back when I was doing just separate core build.<br><br>
</div>Current dependency tree for it includes:<br>
<br>- wildfly-server<br></div>- wildfly-system-jmx<br><br></div>+ arquillian, but that is not a problem anymore given that we moved it out of core and it is not required anymore.<br><br></div>But probably we can revisit that and try to remove it now that there is no need for arq anymore in core.<br>
</div>Big chunk of core testsuite will need to be updated to not use jmx subsystem anymore.<br><br><br></div>Darren, can you create jira for this and assign it to me? I will take look.<br><br>--<br></div>tomaz<br><div><div>
<br>
</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 12:47 PM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Working with the split repo just questioning if JMX is really needed in<br>
core?<br>
<br>
Whilst most distributions would include it I am not convinced it is a<br>
subsystem all must have.<br>
<br>
Regards,<br>
Darran Lofthouse.<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>