Re: Specifying packages in Configuration

2017-07-14 Thread Ralph Goers
It doesn’t sound right to me that they are only loaded once per ClassLoader. That said, I’m not sure how a plugin could be unloaded. Ralph > On Jul 14, 2017, at 12:32 PM, Gary Gregory wrote: > > That is fine by me... > > Based on https://issues.apache.org/jira/browse/LOG4J2-1421 is seems that

Re: Specifying packages in Configuration

2017-07-14 Thread Gary Gregory
That is fine by me... Based on https://issues.apache.org/jira/browse/LOG4J2-1421 is seems that our metadata tooling might be too onerous for some folks, hence the packages option... Gary On Fri, Jul 14, 2017 at 12:16 PM, Matt Sicker wrote: > Maybe packages shouldn't be a configuration file opt

Re: Specifying packages in Configuration

2017-07-14 Thread Matt Sicker
Maybe packages shouldn't be a configuration file option considering the limitations? On 14 July 2017 at 13:58, Gary Gregory wrote: > Hi All: > > We document "packages" as: > > A comma separated list of package names to search for plugins. Plugins are > only loaded once per classloader so changin

Specifying packages in Configuration

2017-07-14 Thread Gary Gregory
Hi All: We document "packages" as: A comma separated list of package names to search for plugins. Plugins are only loaded once per classloader so changing this value may not have any effect upon reconfiguration. That seems quite restrictive: - Start app without "packages" in Log4j config - Reco