Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #169 (new)

Opened 18 years ago

Last modified 9 years ago

Rework logging to use varargs and to silence test output. — at Version 1

Reported by: jamoore Owned by: jamoore
Priority: trivial Milestone: Unscheduled
Component: General Version: 3.0-M2
Keywords: logging, cleanup Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jmoore)

Now that /common and /client are compiling with Java5 (#154) all references to Commons Logging (private static Log log = Logger...) should be replaced by an internal Log class similar to that in Stripes using varargs to prevent the toString() overhead.

While doing this, all tests should be fixed to use logging as well. Depending on what our Log/LogFactory? solution looks like, something along the lines of :

  private static Log TESTLOG = LogFactory.testLogger(MyTest.class);
  // equivalent to
  // TESTLOG = LogFactory.logger("TEST-"+MyTest.class.getName());

That way, all testing could be turned off with:

  log4j.category.TEST = error

or redirected to a file.

Change History (1)

comment:1 Changed 18 years ago by jmoore

  • Description modified (diff)
  • Summary changed from Reworking logging to use varargs to Rework logging to use varargs and to silence test output.
  • Version changed from 3.0-M1 to 3.0-M2
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.76321 sec.)

We're Hiring!