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

        Hide
        Will Glass-Husain added a comment -

        yes, absolutely.

        Show
        Will Glass-Husain added a comment - yes, absolutely.
        Hide
        Nathan Bubna added a comment -

        Makes sense to me. I'll try and find time later today or tomorrow.

        Show
        Nathan Bubna added a comment - Makes sense to me. I'll try and find time later today or tomorrow.
        Hide
        Henning Schmiedehausen added a comment -

        minor is sufficient...

        Show
        Henning Schmiedehausen added a comment - minor is sufficient...

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development