org.apache.logging.log4j.core.appender.ConsoleAppender.createAppender(Layout extends Serializable>, Filter, String, String, String, String)
|
org.apache.logging.log4j.core.appender.SocketAppender.createAppender(String, String, String, SslConfiguration, int, String, String, String, String, String, Layout extends Serializable>, Filter, String, Configuration)
Deprecated in 2.5; use
SocketAppender.createAppender(String, int, Protocol, SslConfiguration, int, int, boolean, String, boolean, boolean, Layout, Filter, boolean, Configuration)
.
|
org.apache.logging.log4j.core.impl.Log4jLogEvent.createEvent(String, Marker, String, Level, Message, Throwable, ThrowableProxy, Map, ThreadContext.ContextStack, String, StackTraceElement, long)
|
org.apache.logging.log4j.core.config.LoggerConfig.createLogger(String, Level, String, String, AppenderRef[], Property[], Configuration, Filter)
|
org.apache.logging.log4j.core.layout.TextEncoderHelper.encodeText(CharsetEncoder, CharBuffer, ByteBufferDestination) |
org.apache.logging.log4j.core.filter.CompositeFilter.getFilters()
|
org.apache.logging.log4j.core.net.MimeMessageBuilder.getMimeMessage()
|
org.apache.logging.log4j.core.config.plugins.util.PluginManager.main(String[])
Use PluginProcessor instead. To do so,
simply include log4j-core in your dependencies and make sure annotation processing is not
disabled. By default, supported Java compilers will automatically use that plugin processor provided
log4j-core is on the classpath.
|
org.apache.logging.log4j.core.util.Assert.requireNonNull(T, String)
Will be removed in 2.5.
|
org.apache.logging.log4j.core.lookup.MapLookup.setMainArguments(String...)
|