You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2010/08/08 05:06:16 UTC

[jira] Resolved: (QPID-1700) The jmx management console core plugin should no longer depend on the jmxremote.sasl plugin, and qpid-managment-common should only depend on it optionally

     [ https://issues.apache.org/jira/browse/QPID-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPID-1700.
----------------------------------

    Resolution: Fixed

> The jmx management console core plugin should no longer depend on the jmxremote.sasl plugin, and qpid-managment-common should only depend on it optionally
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-1700
>                 URL: https://issues.apache.org/jira/browse/QPID-1700
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Management : JMX Console
>    Affects Versions: 0.5
>            Reporter: Robbie Gemmell
>            Assignee: Martin Ritchie
>            Priority: Trivial
>             Fix For: 0.5
>
>
> The jmx management console core plugin should no longer depend on the jmxremote.sasl plugin, and the qpid-managment-common plugin should only depend on it optionally since it is only required for making JMXMP based JMX connections.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org