<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 3:26 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow:hidden">We should sort out the wildfly-server dependency, whatever it is, and<br>
either eliminate it or make it something that relies on an optional<br>
capability.</div></blockquote></div><br><br><div class="gmail_extra">Agreed, most of the hard deps ware because of ARQ container needs, but that is gone now.<br></div>I have most of work done to move it out. just need some more testing.<br>
<br></div><div class="gmail_extra">One thing that looks fishy is Audit logging (part of controller) that has hard coded mgmt paths to JMX subsystem<br></div><div class="gmail_extra">not really sure how this works if jmx is not present.<br>
<br></div><div class="gmail_extra">Kabir, if we move jmx out will there be any issues with that? Beyond fact that audit logging working only when jmx subsystem is present?<br><br>--<br></div><div class="gmail_extra">tomaz<br>
</div></div>