Velocity
  1. Velocity
  2. VELOCITY-499

Default Velocity LogChute implementations blabber too much

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5 beta1, 1.5 beta2
    • Fix Version/s: 1.6
    • Component/s: Engine
    • Labels:
      None

      Description

      While debugging engine code, I noticed that at least the AvalonLogChute (which is the default one if the logkit jar is present which it obviously is in an engine build) logs at [debug] level if there is no explicit configuration present. That is IMHO bad because it swamps an unsuspecting user with a lot of detail that is not needed.

      I propose that we make sure that AvalonLogChute, JdkLogChute, Log4JLogChute and SystemLogChute log only WARN and ERROR level if no configuration is present (default configuration).

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12551955 ] jira [ 12552335 ]
        Mark Thomas made changes -
        Workflow jira [ 12389981 ] Default workflow, editable Closed status [ 12551955 ]
        Nathan Bubna made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Will Glass-Husain made changes -
        Fix Version/s 1.6 [ 12310290 ]
        Nathan Bubna made changes -
        Assignee Nathan Bubna [ nbubna ]
        Henning Schmiedehausen made changes -
        Field Original Value New Value
        Priority Major [ 3 ] Minor [ 4 ]
        Henning Schmiedehausen created issue -

          People

          • Assignee:
            Nathan Bubna
            Reporter:
            Henning Schmiedehausen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development