[wildfly-dev] Update the Logging IDs Page

[Darran Lofthouse]

On 03/07/13 16:58, Tomaž Cerar wrote:
> One of complains we got is about undertow & web subsystem sharing good
> amount of message ids and messages in general.
> Given that web subsystem will be removed soonish, does it make sense to
> change ids for undertow or just keep the old ones (given that they have
> not changed at all)

Are they reporting the same problem and do they have the same solution?

> --
> tomaz
>
>
> On Wed, Jul 3, 2013 at 4:42 PM, Kabir Khan <kabir.khan at jboss.com
> <mailto:kabir.khan at jboss.com>> wrote:
>
>     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:
>
>      > 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:
>      >> On 7/3/13 4:56 AM, Darran Lofthouse wrote:
>      >>> 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?
>      >>>
>      >>> https://community.jboss.org/wiki/LoggingIds
>      >>>
>      >>> 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.
>      >> 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.
>      >>
>      >>> 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
>      >>> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>      >>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>      >>>
>      >>
>      >
>      > _______________________________________________
>      > wildfly-dev mailing list
>      > wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>      > https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>     ---------------------------------------
>     Kabir Khan
>     Prinicipal Software Engineer
>     JBoss by Red Hat
>
>
>     _______________________________________________
>     wildfly-dev mailing list
>     wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>