I think it could be useful in some custom class loading contexts. If the developer is in control of the application, they can set the TCCL as needed when executing in context of an application plugin for example.
On 8 April 2018 at 17:27, Remko Popma <[email protected]> wrote: > I’m not enough of an expert on class loaders to make a judgement call one > way or the other. > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Apr 9, 2018, at 2:32, Gary Gregory <[email protected]> wrote: > > > > Any thoughts on this PR? > > > > Gary > > > > ---------- Forwarded message ---------- > > From: Romain Manni-Bucau <[email protected]> > > Date: Tue, Jan 9, 2018 at 4:00 AM > > Subject: [apache/logging-log4j2] adding log4j2.forceTCLOnly option (#140) > > To: apache/logging-log4j2 <[email protected]> > > Cc: Subscribed <[email protected]> > > > > > > ------------------------------ > > You can view, comment on, or merge this pull request online at: > > > > https://github.com/apache/logging-log4j2/pull/140 > > Commit Summary > > > > - adding log4j2.forceTCLOnly option > > > > File Changes > > > > - *M* log4j-api/src/main/java/org/apache/logging/log4j/util/ > > LoaderUtil.java > > <https://github.com/apache/logging-log4j2/pull/140/files#diff-0> (48) > > - *A* log4j-api/src/test/java/org/apache/logging/log4j/util/ > > LoaderUtilTest.java > > <https://github.com/apache/logging-log4j2/pull/140/files#diff-1> (58) > > - *M* src/site/xdoc/manual/configuration.xml.vm > > <https://github.com/apache/logging-log4j2/pull/140/files#diff-2> (10) > > > > Patch Links: > > > > - https://github.com/apache/logging-log4j2/pull/140.patch > > - https://github.com/apache/logging-log4j2/pull/140.diff > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/apache/logging-log4j2/pull/140>, or mute the thread > > <https://github.com/notifications/unsubscribe-auth/ > ABIfN5qDxD9ZBKTMotzN2RBvxMEAIO87ks5tI0bmgaJpZM4RXp3M> > > . > -- Matt Sicker <[email protected]>
