<div dir="ltr"><div><div><div>Just an update on whole JMX subsystem move thingy.<br><br></div>It is on halt for now, as there is some work going on that in affects JMX and it is easier to have it in same code repo for time beeing<br>
<br></div><div>I will be moved once this is complete.<br></div><div><br></div>--<br></div>tomaz<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 11, 2014 at 12:40 PM, Jeff Mesnil <span dir="ltr"><<a href="mailto:jmesnil@redhat.com" target="_blank">jmesnil@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 24 Jul 2014, at 17:43, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com">tomaz.cerar@gmail.com</a>> wrote:<br>
<br>
> I have send PR removing jmx subsystem from core <a href="https://github.com/wildfly/wildfly-core/pull/57" target="_blank">https://github.com/wildfly/wildfly-core/pull/57</a><br>
><br>
> but to send PR for inclusion to full WildFly repo new release of core is needed as jmx subsystem is using new transformers API we have in core.<br>
<br>
</div>It’s a minor thing but our jconsole.* scripts still live in wildfly repo.<br>
For consistency sake, we should have them in the same repo than the jmx subsystem.<br>
<br>
No need to do anything if we move back jmx to wildfly soon.<br>
But if we decide to keep jmx in wildfly-core, we should move the jconsole scripts there too.<br>
<br>
jeff<br>
<br>
--<br>
Jeff Mesnil<br>
<div class="">JBoss, a division of Red Hat<br>
</div><a href="http://jmesnil.net/" target="_blank">http://jmesnil.net/</a><br>
<div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br></div>