[ https://issues.apache.org/jira/browse/GERONIMO-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578177#action_12578177 ]
syvalta commented on GERONIMO-3898: ----------------------------------- I would prefer having geronimo-internal classes (I consider log4j as such) not visible to applications (at least by default). Currently there's a possibility for version mismatches and classloader issues, if the application includes different version of a library than geronimo has. Is there any plans to implement that (couldn't find anything in Jira)?. I know that it is possible to hide classes by configuration, but to be able to deploy an app without any extra configuration would be nice. > 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.