Commons Logging
  1. Commons Logging
  2. LOGGING-3

Using Log4J as impl. gives linenumbers in Log4JCategoryLog , not class that does the logging.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.0.1
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: PC

      Description

      I use the commons log package and sets the impl=Log4JCategoryLog

      The logging then shows linenumbers in the actual impl class(which bridges the
      logging) and not the class that actually does the logging.

      Thus the same line number appairs all the time(almost) and the feature of log4J
      becomes rather useless.

      This feature is really important in system with lots of code.

        Activity

        Hide
        Richard A. Sitze added a comment -

        This was corrected quite a while back. If you are using the first release,
        try extracting newest code & retrying.

        Show
        Richard A. Sitze added a comment - This was corrected quite a while back. If you are using the first release, try extracting newest code & retrying.
        Hide
        Morten Haavaldsen added a comment -

        The error is present in log4J 1.2.5 together with Commons/Logging 1.0 !

        Please note the LOG4J 1.2.5 is used in COMMONS Logging 1.0 library(no other
        releases).

        The log says linenumbers in the commons class Log4JCategoryLog and not the
        class that does the actual logging.

        The logging works as such....

        Is there a work around using the properties file.

        Show
        Morten Haavaldsen added a comment - The error is present in log4J 1.2.5 together with Commons/Logging 1.0 ! Please note the LOG4J 1.2.5 is used in COMMONS Logging 1.0 library(no other releases). The log says linenumbers in the commons class Log4JCategoryLog and not the class that does the actual logging. The logging works as such.... Is there a work around using the properties file.
        Hide
        Richard A. Sitze added a comment -

        Again, I believe this Log4J functions correctly in 1.0.1 or later.
        Of course, reopen if you find otherwise...

        Show
        Richard A. Sitze added a comment - Again, I believe this Log4J functions correctly in 1.0.1 or later. Of course, reopen if you find otherwise...

          People

          • Assignee:
            Unassigned
            Reporter:
            Morten Haavaldsen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development