The Java 9 module support is still fairly new. We have had reports that it is
still rough around the edges.
Ralph
> On Feb 20, 2018, at 3:06 PM, Matt Sicker wrote:
>
> Log4j 2.10 still requires Java 7. We're planning to require Java 8 only in
> Log4j 3.x. The Java 9 support
I implemented the bindings for SLF4J 1.8 and they are in 2.10.0 but I have
never tried it with OSGi.
Ralph
> On Feb 20, 2018, at 12:47 PM, Rob Gansevles wrote:
>
> Hi,
>
> I am trying to get Log4j 2.10 with slf4j 1.8 working in my eclipse plugin
> project.
>
> Slf4j
To come back to our questions, what version of Log4j are you using?
Are you seeing log entries that are out of order in the same thread?
(Shameless plug) Every java main() method deserves http://picocli.info
> On Feb 21, 2018, at 7:15, Matt Sicker wrote:
>
> On 20 February
Log4j 2.10 still requires Java 7. We're planning to require Java 8 only in
Log4j 3.x. The Java 9 support is so that if you're running in Java 9, you
can take advantage of modules and a couple alternative class
implementations due to new standard APIs ported from formerly internal JDK
APIs.
On 20
Hi,
Would it be possible on this dependencies
page:https://logging.apache.org/log4j/2.0/runtime-dependencies.html
to specify if v2.10.0 still works with Java 7 or 8 as stated for v2.9.1 or
mostly Java 9 is now targeted? And if there could be now some side effects with
Java 8 (like LOG4J2-2129)
Hi,
I am trying to get Log4j 2.10 with slf4j 1.8 working in my eclipse plugin
project.
Slf4j 1.8 does not use the StaticLoggerBinder method anymore and it seems
to me osgi was depending on that.
It worked fine with Log4j 2.9 and slf4j 1.7
The error I get is the No-SLF4J-providers-were-found
That was it! Thanks.
Next question: When I do this:
LoggerContext loggerContext =
(LoggerContext)LogManager.getContext(false);
Configuration loggerConfiguration = loggerContext.getConfiguration();
Map appendersType =
In the case of a multi threaded application, not async, would it be
possible to have avoid the potential mis ordering by having a 500ms (for
example) window of collection for log events, and instead of logging the
next log event in the queue, the logic would be search for the oldest event
in the
Do you mean something like this?
public class MainApplication {
public static void main(String[] args) throws Exception {
Logger logger = LogManager.getLogger(MainApplication.class);
// logging level is error
logger.error("msg1");
logger.info("msg2");
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to a user@ or
dev@ list of one or more Apache Software Foundation projects.)
We’re pleased to announce the upcoming ApacheCon [1] in Montréal,
September 24-27. This event is all about you — the Apache project
10 matches
Mail list logo