[Bug 24] New: Constants need to be grouped
http://bugzilla.qos.ch/show_bug.cgi?id=24 Summary: Constants need to be grouped Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P1 Component: Joran AssignedTo: logback-dev@qos.ch ReportedBy: noreply.sebastien@qos.ch The constants used by modules to put objects in the context's object map come from different classes. For example, ActionConst.APPENDER_BAG is the constant used by c.q.l.core.joran.AppenderAction, and c.q.l.core.CoreGlobal.EVALUATOR_MAP is used by classes trying to add or access evaluators mapped in the context. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.qos.ch/show_bug.cgi?id=24 ------- Comment #1 from noreply.ceki@qos.ch 2006-10-31 13:35 ------- Regrouping these contants at a single points sounds like a good idea. How about c.q.l.core.CoreGlobal ? -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.qos.ch/show_bug.cgi?id=24 ------- Comment #2 from noreply.sebastien@qos.ch 2006-11-30 17:24 ------- This needs further reflection. There is arguably a "context" linking constants in ActionConst, for examples. Since the object map in the context is supposed to be generic, should the core module keep an eye on who's putting what where? Moving APPENDER_BAG in CoreGlobal leeds to moving other constants of the same class, and we do not want CoreGlobal to become the place where constants are alltogether... -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
participants (1)
-
bugzilla-daemon＠pixie.qos.ch