[jira] [Closed] (LOG4J2-1506) Unregister JMX ignores log4j2.disable.jmx property

[ https://issues.apache.org/jira/browse/LOG4J2-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Schleger closed LOG4J2-1506. - > Unregister JMX ignores log4j2.disable.jmx property > --

Re: [jira] [Commented] (LOG4J2-1549) AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true

Yes. The fix is already in master branch. On Thu, Aug 25, 2016 at 6:16 AM, Remko Popma (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/LOG4J2-1549?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=15436260#comment-15436260 ] > > Remko Popm

Re: [jira] [Commented] (LOG4J2-1549) AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true

Or rather, I fixed it for ConfigurationBuilder. I haven't tested if that fixes it for PropertiesConfigurationBuilder as well, but I guess it will. On Thu, Aug 25, 2016 at 9:52 AM, Mikael Ståldal wrote: > Yes. The fix is already in master branch. > > On Thu, Aug 25, 2016 at 6:16 AM, Remko Popma (

[jira] [Updated] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierrick HYMBERT updated LOG4J2-1320: - Attachment: LOG4J2-1320-3.patch # Added set of unit tests for {{org.apache.logging.log4j

[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436576#comment-15436576 ] Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:39 AM:

[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436576#comment-15436576 ] Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:39 AM:

[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436576#comment-15436576 ] Pierrick HYMBERT edited comment on LOG4J2-1320 at 8/25/16 9:40 AM:

[jira] [Updated] (LOG4J2-1548) [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierrick HYMBERT updated LOG4J2-1548: - Attachment: LOG4J2-1548-testcase-2.patch Done. Added a constant {{RollingAppenderCronOnce

Re: [jira] [Commented] (LOG4J2-1549) AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true

Good stuff! FYI, your reply is not visible on the Jira. Sent from my iPhone > On 2016/08/25, at 16:53, Mikael Ståldal wrote: > > Or rather, I fixed it for ConfigurationBuilder. I haven't tested if that > fixes it for PropertiesConfigurationBuilder as well, but I guess it will. > >> On Thu, A

[jira] [Commented] (LOG4J2-1549) AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true

[ https://issues.apache.org/jira/browse/LOG4J2-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436783#comment-15436783 ] Mikael Ståldal commented on LOG4J2-1549: I fixed it for ConfigurationBuilder. I h

Question about old issues that never had a jira ticket or changelog entry

Back during the 2.0 and 2.1 releases, I wasn't very active in using jira, and there were a lot of plugin-related features that I never really added to the changelog. Would it be worth going back and adding tickets for those old features? -- Matt Sicker

Re: Question about old issues that never had a jira ticket or changelog entry

Only if the issues are going to contain significant documentation on what was done. The main thing would be if we want to search Jira to find out about some feature. Ralph > On Aug 25, 2016, at 9:08 AM, Matt Sicker wrote: > > Back during the 2.0 and 2.1 releases, I wasn't very active in using

Re: Question about old issues that never had a jira ticket or changelog entry

I was thinking about the plugin builder mechanism (which was recently documented in more detail), the validation annotations, might be some more that I'm not remembering. On 25 August 2016 at 11:13, Ralph Goers wrote: > Only if the issues are going to contain significant documentation on what >

[jira] [Commented] (LOG4J2-1317) Add ability for lookups to use defaults for other values than null

[ https://issues.apache.org/jira/browse/LOG4J2-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437180#comment-15437180 ] Andrei Ivanov commented on LOG4J2-1317: --- Uf, it's problematic with the amount of ti

[jira] [Updated] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1523: --- Description: Support all appenders in Log4j 1 to the extent possible and reasonable. All app

[jira] [Updated] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1523: --- Description: Support all appenders in Log4j 1 to the extent possible and reasonable. All app

[jira] [Commented] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437528#comment-15437528 ] Ralph Goers commented on LOG4J2-1523: - http://people.apache.org/~carnold/log4j/docs/x

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437550#comment-15437550 ] Gary Gregory commented on LOG4J2-1320: -- Thank you for the patch. I've applied the pa

[jira] [Commented] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437554#comment-15437554 ] Ralph Goers commented on LOG4J2-1523: - Also, I think you only need to support the Log

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437594#comment-15437594 ] Gary Gregory commented on LOG4J2-1320: -- [~phymbert]: Please verify and close. If you

[jira] [Updated] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1523: --- Description: Support all appenders in Log4j 1 to the extent possible and reasonable. All app

[jira] [Assigned] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1523: -- Assignee: Mikael Ståldal > Log4j 1 appenders > - > > K

Jenkins build became unstable: Log4j 2.x #2211

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Reopened] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1320: -- [~phymbert]: We have some failures: https://builds.apache.org/job/Log4j%202.x/org.apache.logging.l

[jira] [Comment Edited] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437666#comment-15437666 ] Gary Gregory edited comment on LOG4J2-1320 at 8/25/16 9:04 PM:

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437666#comment-15437666 ] Gary Gregory commented on LOG4J2-1320: -- The problem is probably this in the test: {{

Jenkins build is still unstable: Log4j 2.x #2212

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Jenkins build is still unstable: Log4j 2.x #2212

I have a pending fix for that. Please hold. Gary On Thu, Aug 25, 2016 at 2:11 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > > - > To unsubscribe, e-ma

[jira] [Resolved] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1547. -- Resolution: Fixed In Git master. Please review. > The Core AbstractConfiguration should track

[jira] [Updated] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1547: - Description: The class in Core, {{AbstractConfiguration}}, should track its {{LoggerContext}} an

[jira] [Updated] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1547: - Summary: The Core AbstractConfiguration should track its LoggerContext and add Configuration.getL

Jenkins build is back to stable : Log4j 2.x #2213

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437854#comment-15437854 ] Matt Sicker commented on LOG4J2-1547: - I know that log4j-core's APIs are strongly bac

[jira] [Comment Edited] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437854#comment-15437854 ] Matt Sicker edited comment on LOG4J2-1547 at 8/25/16 10:39 PM:

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437862#comment-15437862 ] Gary Gregory commented on LOG4J2-1547: -- The problem is there is apparently not a rel

[jira] [Comment Edited] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437862#comment-15437862 ] Gary Gregory edited comment on LOG4J2-1547 at 8/25/16 10:45 PM: ---

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437927#comment-15437927 ] Gary Gregory commented on LOG4J2-1547: -- But... if you think some ctors are that impo

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437926#comment-15437926 ] Gary Gregory commented on LOG4J2-1547: -- Hi, WRT "We could remove the deprecated met

[jira] [Issue Comment Deleted] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1547: - Comment: was deleted (was: But... if you think some ctors are that important, then I'm all ears ;

[jira] [Comment Edited] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437926#comment-15437926 ] Gary Gregory edited comment on LOG4J2-1547 at 8/25/16 10:51 PM: ---

[jira] [Resolved] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1320. -- Resolution: Fixed Test fixed. Please verify and close the ticket overall. > Custom plugins ar

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438126#comment-15438126 ] Remko Popma commented on LOG4J2-1547: - Gary, Can you add text to the manual pages for

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438148#comment-15438148 ] Remko Popma commented on LOG4J2-1547: - I agree with Matt that we should try to make t

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438163#comment-15438163 ] Ralph Goers commented on LOG4J2-1547: - Unfortunately, this is one of the downsides of

[jira] [Comment Edited] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438163#comment-15438163 ] Ralph Goers edited comment on LOG4J2-1547 at 8/25/16 11:57 PM:

[jira] [Commented] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438177#comment-15438177 ] Gary Gregory commented on LOG4J2-1540: -- For this next step I see two approaches: -

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438175#comment-15438175 ] Gary Gregory commented on LOG4J2-1547: -- OK, I am happy to leave this commit as is :-

[jira] [Comment Edited] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438177#comment-15438177 ] Gary Gregory edited comment on LOG4J2-1540 at 8/26/16 12:13 AM: ---

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438203#comment-15438203 ] Gary Gregory commented on LOG4J2-1547: -- Hi Remko, The LoggerConfig class has not c

[jira] [Comment Edited] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438177#comment-15438177 ] Gary Gregory edited comment on LOG4J2-1540 at 8/26/16 12:39 AM: ---

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438292#comment-15438292 ] Matt Sicker commented on LOG4J2-1547: - Well, my idea here was to deprecate for 2.7, i

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438384#comment-15438384 ] Remko Popma commented on LOG4J2-1547: - I meant Configuration. > The Core AbstractCo

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438388#comment-15438388 ] Remko Popma commented on LOG4J2-1547: - If we know we will break existing programmatic

[jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438417#comment-15438417 ] Gary Gregory commented on LOG4J2-1547: -- Hi Remko: When I think of programmatic conf

Unused name arg in ConfigurationFactory.getConfiguration(LoggerContext, String, URI)

Hi All, In the API: org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(LoggerContext, String, URI) The name arg is not used but the API is reimplemented by subclasses but it does not seem to be used except in a unit test. Is the fact that it is not used a bug or just lef

Tying up loose ends with AbstractConfiguration.AbstractConfiguration(LoggerContext, ConfigurationSource)

Hi All: I'd like to tied up some loose end with Tying up loose ends with AbstractConfiguration.AbstractConfiguration(LoggerContext, ConfigurationSource) There are three call sites that do this: -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edit

[jira] [Commented] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438435#comment-15438435 ] Ralph Goers commented on LOG4J2-1540: - Why not just add Configuration to the FactoryD

Fwd: Tying up loose ends with AbstractConfiguration.AbstractConfiguration(LoggerContext, ConfigurationSource)

[oops, sent too soon] Hi All: I'd like to tie up a loose end with callers of AbstractConfiguration. AbstractConfiguration(LoggerContext, ConfigurationSource) There are four call sites that do this: super(null, ConfigurationSource.NULL_SOURCE); These are: - org.apache.logging.log4j.core.BasicC

[jira] [Commented] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438438#comment-15438438 ] Gary Gregory commented on LOG4J2-1540: -- OK, that's my 2nd bullet point. Seems reason

Re: Unused name arg in ConfigurationFactory.getConfiguration(LoggerContext, String, URI)

It is used in private Configuration getConfiguration(final LoggerContext loggerContext, final boolean isTest, final String name) Ralph > On Aug 25, 2016, at 8:51 PM, Gary Gregory wrote: > > Hi All, > > In the API: > > org.apache.logging.log4j.core.config.ConfigurationFactory.getConfigurati

Re: Tying up loose ends with AbstractConfiguration.AbstractConfiguration(LoggerContext, ConfigurationSource)

CompositeConfiguration doesn’t look correct to me. It makes sense for it to have a null source, but I’m not sure why it should have a null LoggerContext.I think it should be: super(configurations.get(0).getLoggerContext(), ConfigurationSource.NULL_SOURCE); Either that or getLoggerContext() sho

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438504#comment-15438504 ] Pierrick HYMBERT commented on LOG4J2-1320: -- Hi [~garydgregory], Perfect, it wil

[jira] [Commented] (LOG4J2-1320) Custom plugins are not loaded, URL protocol vfs is not supported

[ https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438518#comment-15438518 ] Gary Gregory commented on LOG4J2-1320: -- Ah, right. If you post the new description h