[jboss-jira] [JBoss JIRA] (JGRP-1611) Update logging to follow TAG-2 message format
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Fri Aug 30 12:35:03 EDT 2013
[ https://issues.jboss.org/browse/JGRP-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro resolved JGRP-1611.
--------------------------------
Resolution: Done
(3.2.x branch)
https://github.com/belaban/JGroups/pull/101
(master)
https://github.com/belaban/JGroups/pull/102
> Update logging to follow TAG-2 message format
> ---------------------------------------------
>
> Key: JGRP-1611
> URL: https://issues.jboss.org/browse/JGRP-1611
> Project: JGroups
> Issue Type: Task
> Reporter: James Perkins
> Assignee: Paul Ferraro
> Priority: Minor
> Fix For: 3.4
>
>
> As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list