Dominik Psenner wrote on 23.08.2016 13:48:13:
> Von: Dominik Psenner
> An: log4net-dev@logging.apache.org
> Datum: 23.08.2016 13:49
> Betreff: Re: PluginMap survives
LoggerRepositorySkeleton.ResetConfiguration()
>
> --8<---8<
hwarz.com wrote:
Stefan Bodewig wrote on 23.08.2016 06:05:23:
> Von: Stefan Bodewig
> An: "Log4Net Developers List"
> Datum: 23.08.2016 06:06
> Betreff: Re: PluginMap survives
LoggerRepositorySkeleton.ResetConfiguration()
>
> On 2016-08-22, wrote:
>
> > The
Stefan Bodewig wrote on 23.08.2016 06:05:23:
> Von: Stefan Bodewig
> An: "Log4Net Developers List"
> Datum: 23.08.2016 06:06
> Betreff: Re: PluginMap survives
LoggerRepositorySkeleton.ResetConfiguration()
>
> On 2016-08-22, wrote:
>
> > The question is
On 2016-08-22, wrote:
> The question is: Is this the right way to do, or are there strong
> reasons for the plugins to stay?
TBH I have no idea.
It might be the case that some people out there rely on this
behavior. One indicator for this might be that you are the first person
after twelve year
Hard to tell. Worst case is that we implicitly break code that relies on
plugins to stay where they are. It seems logical to me that
ResetConfiguration() should reset all the configuration. Now one could
argue that plugins are not part of the configuration, but rather something
that provides functi
