[
https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755280#comment-13755280
]
Nick Williams edited comment on LOG4J2-293 at 8/31/13 12:09 AM:
----------------------------------------------------------------
Your IDE has reformatted the JavaDoc and Java code in the file. This makes it
very difficult to separate out the changes you made from the reformatting.
Please correct this. Patches should not reformat code that doesn't change. You
will likely need to disable this auto-reformatting in your IDE, or change the
settings to reflect the Log4j coding standards (for example, 120-character
lines, not 80-character lines as it appears your IDE is enforcing).
was (Author: beamerblvd):
Your IDE has reformatted the JavaDoc and Java code in the file. This makes
in very difficult to separate out the changes you made from the reformatting.
Please correct this. Patches should not reformat code that doesn't change. You
will likely need to disable this auto-reformatting in your IDE, or change the
settings to reflect the Log4j coding standards (for example, 120-character
lines, not 80-character lines as it appears your IDE is enforcing).
> classloader URI scheme broken or insufficient when using Log4jContextListener
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-293
> URL: https://issues.apache.org/jira/browse/LOG4J2-293
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-beta7
> Reporter: Neale Upstone
> Assignee: Nick Williams
> Labels: documentation
> Attachments: ConfigurationFactory.java, LOG4J2-293.patch,
> TestConfigurator.java
>
>
> I'm trying to migrate to Log4j2, and things looked promising when I spotted
> Log4jContextListener.
> However, there are too many holes.
> Firstly, I tried using classpath: as a scheme, and nothing blew up, so I
> assumed I'd got it right.
> Then I *looked at the code* (which shouldn't be how we find out) and
> eventually discovered some code relating to a 'classloader' scheme.
> Still silent failure. It seems that the classpath is not being searched,
> perhaps just the WAR classloader, not the JARs in WEB-INF/lib.
> Next I tried omitting the / (i.e. using classloader:log4j2.xml) and got a
> NullPointerException.
> Can you please document what schemes are supported and what you expect them
> to do, and *not fail silently* when a configuration file is specified, but
> nothing happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
