[wildfly-dev] Update the Logging IDs Page
David M. Lloyd
david.lloyd at redhat.com
Fri Jul 5 11:32:38 EDT 2013
On 7/3/13 11:29 AM, Darran Lofthouse wrote:
> On 03/07/13 17:22, Tomaž Cerar wrote:
>> On Wed, Jul 3, 2013 at 6:04 PM, Darran Lofthouse
>> <darran.lofthouse at jboss.com <mailto:darran.lofthouse at jboss.com>> wrote:
>> Are they reporting the same problem and do they have the same solution?
>> They are exactly the same, same id and msg....
> That wasn't my question ;-)
> Do they have the same meaning and same solution?
> Or if someone searches based on these IDs is it going to mean something
> different when it applies to Undertow?
I want to dodge this problem by redoing all of our log IDs before the
next beta release. Here's what I want to do:
1) Create a filtered _private subpackage in each WildFly module
2) Move all log messages to a single interface per modules
3) Renumber every log message, changing the project code from JBAS to
WFXXX where XXX is a sub-identifier for the module (e.g.
4) Create a mapping document which shows the mapping from JBAS messages
to the new codes, which can be used to seed KBs or whatever
5) Going forward, we will coordinate message IDs across different
project forks by using comments to block out IDs that exist only in
non-mainline forks (EAP) (but since WildFly will have new codes, it is
unlikely that the EAP 6.x cycle will introduce any conflicts; at most
we'll have to add new codes to the mapping doc from time to time when
fixes are backported)
I have already expressed some or all of this but I don't remember where
or when. ;) But hopefully this will shed some light. Or perhaps add
some confusion :)
More information about the wildfly-dev