[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037073#comment-14037073
]
Abid commented on LOG4J2-461:
-----------------------------
Got an update from Oracle which essentially means that packaging of library
jars with the security provider is not supported; library jars for security
provider have to go into server classpath in one way or the other.
For me this would mean taking risk of exposing those jars at global level to
whole bunch of multi-vendor applications (deployed into weblogic environment)
who use their own different versions of log4j libraries.
Oracle raised an Enhancement Request of low severity in this regard :(
> ERROR StatusLogger Unable to locate a logging implementation, using
> SimpleLogger
> ---------------------------------------------------------------------------------
>
> Key: LOG4J2-461
> URL: https://issues.apache.org/jira/browse/LOG4J2-461
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.0-beta9, 2.0-rc1
> Environment: Android
> Reporter: Gaurav Kapoor
> Priority: Blocker
> Attachments: MANIFEST.MF
>
>
> ERROR StatusLogger Unable to locate a logging implementation, using
> SimpleLogger
> Code:
> Logger LOG = LogManager.getLogger(MainActivity.class);
> LOG.error("Test Log4j2");
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <Configuration>
> <Appenders>
> <Console name="STDOUT" target="SYSTEM_OUT">
> <PatternLayout pattern="%d %-5p [%t] %C{2} (%F:%L) - %m%n"/>
> </Console>
> </Appenders>
> <Loggers>
> <Logger name="hello" level="info"/>
> <Root level="trace">
> <AppenderRef ref="STDOUT"/>
> </Root>
> </Loggers>
> </Configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
