<div dir="ltr"><div><div>Any special reason we are sticking with org.jboss.as.* categories for all the logging stuff?<br></div>given that we are refactoring everything to have different logging codes, we could do change to org.wildfly.* as well.<br>
<br></div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 7:45 PM, David M. Lloyd <span dir="ltr"><<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yeah this is a raw, tab-delimited, N:1 mapping of old codes to new<br>
codes. I'm hoping that this form will be transmutable into any form we<br>
need with a minimum of headache. Here's a better link that will evolve<br>
with the PR:<br>
<br>
<a href="https://github.com/dmlloyd/wildfly/blob/wfly-2864-log-messages/log-ids.txt" target="_blank">https://github.com/dmlloyd/wildfly/blob/wfly-2864-log-messages/log-ids.txt</a><br>
<br>
Note that the final PR doesn't have to include this file (and probably<br>
shouldn't), but it was a good way to track the ID mappings per commit.<br>
<div class="HOEnZb"><div class="h5"><br>
On 02/12/2014 12:34 PM, James R. Perkins wrote:<br>
> Not sure on the final plans on how to present it, but currently there is<br>
> <a href="https://github.com/dmlloyd/wildfly/blob/cf6775eb53204b8bdad4e5cd9d3445bd1395b6fa/log-ids.txt" target="_blank">https://github.com/dmlloyd/wildfly/blob/cf6775eb53204b8bdad4e5cd9d3445bd1395b6fa/log-ids.txt</a><br>
> in the root directory.<br>
><br>
> On 02/12/2014 10:26 AM, Brian Stansberry wrote:<br>
>> What's the plan re: item 4 from your post at [1] from last July?<br>
>><br>
>> "4) Create a mapping document which shows the mapping from JBAS messages<br>
>> to the new codes, which can be used to seed KBs or whatever"<br>
>><br>
>> On 2/12/14, 9:50 AM, David M. Lloyd wrote:<br>
>>> It's right there in the topic. James and I have carried out the change<br>
>>> discussed in [1] and elsewhere, and have split all the old "JBAS" codes<br>
>>> into specific "WFLYxxx" codes. The pull request is divided into one<br>
>>> commit per Maven module for easier review.<br>
>>><br>
>>> I request that every subsystem or component maintainer please review the<br>
>>> part of the commit that pertains to their piece, and please post<br>
>>> comments on the PR itself [2].<br>
>>><br>
>>> In addition, I want to discuss a few cases where modules are using<br>
>>> message bundles and loggers from neighboring modules. This is going to<br>
>>> become a problem when we do the distribution split-up.<br>
>>><br>
>>> Finally, one small matter I want to sort out is that we have several<br>
>>> modules which use a project-specific code for IllegalArugmentExceptions<br>
>>> that pertain specifically to null parameters, whereas some do not use a<br>
>>> code for this case and just throw the exception.<br>
>>><br>
>>> My feeling is we should either (a) don't use a code for this kind of<br>
>>> thing, or (b) come up with a "common" module or code space+project code<br>
>>> which every project can reuse, so we just have one code that universally<br>
>>> means "the parameter can't be null".<br>
>>><br>
>>> [1] <a href="http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000428.html" target="_blank">http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000428.html</a><br>
>>> [2] <a href="https://github.com/wildfly/wildfly/pull/5906" target="_blank">https://github.com/wildfly/wildfly/pull/5906</a><br>
>>><br>
>><br>
><br>
<br>
<br>
--<br>
</div></div><span class="HOEnZb"><font color="#888888">- DML<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>