[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763389#comment-12763389 ] 

Radoslav Husar commented on MODCLUSTER-315:
-------------------------------------------

This is rather a peculiar situation, because master (1.2.3.Beta1) is older than 1.2.x branch.

This issue is only fixed in master though and not in the tag (at least I dont see it): https://github.com/modcluster/mod_cluster/commits/1.2.3.Final
                
> Convert project to use i18n logging and exceptions
> --------------------------------------------------
>
>                 Key: MODCLUSTER-315
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-315
>             Project: mod_cluster
>          Issue Type: Task
>            Reporter: James Perkins
>            Assignee: Paul Ferraro
>
> 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