<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">We actually need a report (/guard) that
goes across multiple versions (including EAP).<br>
<br>
Carlo<br>
<br>
On 07/04/2013 02:35 AM, James R. Perkins wrote:<br>
</div>
<blockquote cite="mid:51D4C36C.5000406@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 07/03/2013 07:42 AM, Kabir Khan
wrote:<br>
</div>
<blockquote
cite="mid:0C4A571D-C28C-4D2A-A517-DE08286FB41C@jboss.com"
type="cite">
<pre wrap="">I also had a vague thought about this. Perhaps the logging annotation processor could be changed to dump a target/logging-ids.txt file for each subsystem, which we could then use to do a check at the end of the build.
On 3 Jul 2013, at 15:19, Jaikiran Pai wrote:</pre>
</blockquote>
There is actually LOGTOOL JIRA (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://issues.jboss.org/browse/LOGTOOL-74">https://issues.jboss.org/browse/LOGTOOL-74</a>)
to generate reports of the log id and message. I haven't done
anything with it yet, but a simple text file would be easy enough.
My initial thought was to feed a format in since it would
essentially become a table of some sort.<br>
<blockquote
cite="mid:0C4A571D-C28C-4D2A-A517-DE08286FB41C@jboss.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">I wonder, if we could somehow integrate these checks and maintaining of
the range, within the build. I _think_ it should be possible to do it,
but I haven't thought much about it yet.
-Jaikiran
On Wednesday 03 July 2013 07:47 PM, Brian Stansberry wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 7/3/13 4:56 AM, Darran Lofthouse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
Recently we have had some issues reported where logging IDs are
suspected to be duplicates.
Can I suggest that one thing we do need is to update the page tracking
the reserved ID's to make it easier to identify what block is available
next?
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://community.jboss.org/wiki/LoggingIds">https://community.jboss.org/wiki/LoggingIds</a>
Would it would be easier if the ranges column was sequential, if a
subsystem takes multiple allocations then it should just appear in the
list more than once.
</pre>
</blockquote>
<pre wrap="">If I understand what you're saying correctly, what you describe is the
way it's meant to be. A quick scan shows it follows that pattern, except
for CMP which didn't have multiple lines in the table. I fixed that. If
there are others that don't follow the pattern they should be fixed.
</pre>
<blockquote type="cite">
<pre wrap="">At the moment to find a free block you need to
scan up and down the page to check the subsequent allocations.
Regards,
Darran Lofthouse.
_______________________________________________
wildfly-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
<pre wrap="">---------------------------------------
Kabir Khan
Prinicipal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
James R. Perkins
Red Hat JBoss Middleware</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>