You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/01/28 18:43:59 UTC
[jira] Created: (QPID-1619) Make QMan package friendly
Make QMan package friendly
--------------------------
Key: QPID-1619
URL: https://issues.apache.org/jira/browse/QPID-1619
Project: Qpid
Issue Type: Improvement
Components: Java Management : QMan
Affects Versions: M5
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: M5
Certain changes done before to make QMan package friendly has been removed accidently.
This JIRA attempts to do the following
1 Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm.
(Currently Qpid is does not have component based release artifacts, but in the future we plan to do that. When that happens, users should be able download a standalone qman-jmx installation.
2. Add a man page for qman-jmx (this was deleted, so adding back a modified version)
3. Add a simple log4j file for qman-jmx.
--
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
[jira] Resolved: (QPID-1619) Make QMan package friendly
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-1619.
------------------------------------
Resolution: Fixed
Thanks Andrea for the comments.
For this time around we could have the two different log4j files, but going forward we can unify it and have one single file in the xml format.
I will resolve this ticket as the changes I had made have already made in to the QMan packages.
For any other issues arising in the future we could open a new JIRA and track them.
> Make QMan package friendly
> --------------------------
>
> Key: QPID-1619
> URL: https://issues.apache.org/jira/browse/QPID-1619
> Project: Qpid
> Issue Type: Improvement
> Components: Java Management : QMan
> Affects Versions: M5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
>
> Certain changes done before to make QMan package friendly has been removed accidently.
> This JIRA attempts to do the following
> 1 Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm.
> (Currently Qpid is does not have component based release artifacts, but in the future we plan to do that. When that happens, users should be able download a standalone qman-jmx installation.
> 2. Add a man page for qman-jmx (this was deleted, so adding back a modified version)
> 3. Add a simple log4j file for qman-jmx.
--
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
[jira] Updated: (QPID-1619) Make QMan package friendly
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1619:
---------------------------------
Fix Version/s: (was: M5)
> Make QMan package friendly
> --------------------------
>
> Key: QPID-1619
> URL: https://issues.apache.org/jira/browse/QPID-1619
> Project: Qpid
> Issue Type: Improvement
> Components: Java Management : QMan
> Affects Versions: M5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
>
> Certain changes done before to make QMan package friendly has been removed accidently.
> This JIRA attempts to do the following
> 1 Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm.
> (Currently Qpid is does not have component based release artifacts, but in the future we plan to do that. When that happens, users should be able download a standalone qman-jmx installation.
> 2. Add a man page for qman-jmx (this was deleted, so adding back a modified version)
> 3. Add a simple log4j file for qman-jmx.
--
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
[jira] Commented: (QPID-1619) Make QMan package friendly
Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672898#action_12672898 ]
Andrea Gazzarini commented on QPID-1619:
----------------------------------------
R: Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm.
A : Right! And I think I should do the same for qman-wsdm-start.sh. If you agree I'll rename that script too.
R: (Currently Qpid is does not have component based release artifacts, but in the future we plan to do that.
A: Of course I completely agree with this point :) QMan should be a separated artifact. If I need a broker I want download just a broker. And in addition QMan WS-DM is not tied on any specific language bind (java or c++) but it is able to talk in an language-independent way.
R: When that happens, users should be able download a standalone qman-jmx installation.
A: Here we should decide the level of granularity of the artifact(s). At the moment the ant build-release-bin is producing a distribution that contains both QMan WS-DM and JMX version. So if we want two separated dists a change needs to be made in build.xml in order to accomodate that need.
My question is : the whole bundle is (at the moment but I don't believe it will change) 19M...is so big?
R: Add a man page for qman-jmx (this was deleted, so adding back a modified version)
A: Right of course and excuse me again for deletion...BTW for who is reading the description of this issue : Rajith left me anonymous : "has been removed accidently" means "Andrea has removed that accindently" :)
R: Add a simple log4j file for qman-jmx.
A: As QMan JMX is included on QMan WS-DM the log4j.xml shipped under /etc directory is configuring logging for JMX core too so my questions are :
- why don't we leave log4j.xml only?
- if we decide to ship two separated files why don't we use the same format? I think XML is pretty straightforward
Andrea
> Make QMan package friendly
> --------------------------
>
> Key: QPID-1619
> URL: https://issues.apache.org/jira/browse/QPID-1619
> Project: Qpid
> Issue Type: Improvement
> Components: Java Management : QMan
> Affects Versions: M5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M5
>
>
> Certain changes done before to make QMan package friendly has been removed accidently.
> This JIRA attempts to do the following
> 1 Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm.
> (Currently Qpid is does not have component based release artifacts, but in the future we plan to do that. When that happens, users should be able download a standalone qman-jmx installation.
> 2. Add a man page for qman-jmx (this was deleted, so adding back a modified version)
> 3. Add a simple log4j file for qman-jmx.
--
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