Use slf4j as the logging mechanism across all code paths
Key: QPID-2831
URL: https://issues.apache.org/jira/browse/QPID-2831
Project: Qpid
Issue Type: Improvement
Affects
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: qpid-2824_1.patch
This is for the test suite - AbstractTestMessages is modified to use
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: (was: qpid-2824_1.patch)
Use toLogString rather than toString on LogSubject(s) and add
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: (was: qpid-2824.patch)
Use toLogString rather than toString on LogSubject(s) and add a
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: qpid-2824.patch
Patch combining the previous 2 patches and fixing tests.
Use toLogString
On 08/27/2010 07:55 PM, a fabbri wrote:
Does anyone regularly build the linux C++ stuff outside of the source tree?
That is, you're supposed to be able to run configure and make from a
build directory outside of qpid/cpp. I seem to have more build issues
this way though.
I always build
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: (was: qpid-2824.patch)
Use toLogString rather than toString on LogSubject(s) and add a
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2824:
--
Attachment: qpid-2824.patch
Use toLogString rather than toString on LogSubject(s) and add a new
Collate all the LogSubject format in a static class
---
Key: QPID-2832
URL: https://issues.apache.org/jira/browse/QPID-2832
Project: Qpid
Issue Type: Improvement
Components: Java
[
https://issues.apache.org/jira/browse/QPID-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2832:
--
Summary: Collate all the LogSubject formatting strings in a static class
(was: Collate all the
[
https://issues.apache.org/jira/browse/QPID-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2832:
--
Attachment: qpid-2832.patch
Collate all the LogSubject formatting strings in a static class
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-2824:
-
Summary: Use toLogString rather than toString on LogSubject(s) (was:
Use toLogString rather
[
https://issues.apache.org/jira/browse/QPID-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-2824.
--
Resolution: Fixed
Patch applied.
Use toLogString rather than toString on LogSubject(s)
Add a Generic Actor for 0-10 Logging
Key: QPID-2833
URL: https://issues.apache.org/jira/browse/QPID-2833
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.7
[
https://issues.apache.org/jira/browse/QPID-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2833:
--
Attachment: qpid-2833.patch
Add a Generic Actor for 0-10 Logging
[
https://issues.apache.org/jira/browse/QPID-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved QPID-2481.
Fix Version/s: 0.7
Resolution: Fixed
This issue was fixed in 0.7 by Ken Giusti around r934561.
[
https://issues.apache.org/jira/browse/QPID-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved QPID-2827.
Assignee: Ted Ross
Fix Version/s: 0.7
Resolution: Fixed
QPID Cpp WinSDK does not contain
Hi QPid Dev,
I'm trying to get qpid going in a virtual environment on Ubuntu 8.04, python
2.5. I was encountering the following exception:
ValueError: unknown url type: /home/myhomedir/specs/amqp.0-10.dtd
...when doing a regular import of qpid.
I found message threads discussing the same
On Fri, Aug 27, 2010 at 4:13 PM, Steve Huston shus...@riverace.com wrote:
Hi Marnie,
I'd like to propose a timeline for the next Qpid release -
with a target of end October.
IIRC, we usually take trunk as stable/defect fixing only for
2 weeks before release so that would take us back to
19 matches
Mail list logo