geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3898) Provide handy way to configure log4j for a particular app
Date Thu, 13 Mar 2008 07:11:46 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-3898.
----------------------------------

    Resolution: Fixed

branches 2.1 rev 636646, trunk rev 636647 make the gbean actually work.

plugins/directory/branches/1.0 converted to g 2.1.1-SNAPSHOT and use of this gbean to segregate
apacheds logging rev 636649

> Provide handy way to configure log4j for a particular app
> ---------------------------------------------------------
>
>                 Key: GERONIMO-3898
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3898
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Logging
>    Affects Versions: 2.1.1, 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.1.1, 2.2
>
>
> It may or may not be obvious to people how to configure log4j for their app without breaking
geronimo's log setup.  We can easily provide a gbean that reads a property file, removes stuff
that applies to global logging, and feeds the rest to log4j.  Then people can supply a properties
file for their apps log4j configuration, either in the classpath or var/<somewhere>.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message