I created LOG4J2-1836 to address this. Ralph
> On Mar 3, 2017, at 12:01 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Likewise, I suspect that ProviderUtil should only list 2.6.0 as a compatible > version since the implementation must be at that level or higher. > > Ralph > >> On Mar 3, 2017, at 11:58 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> The Log4jAPIVersion in log4j-provider.properties in log4j-core says it >> supports the 2.1.0 API. Is that actually correct? I suspect that if you try >> to use the log4j 2.1 API jar with the log4j 2.8.1 core jar there will be >> problems. Doesn’t Log4j core require a Log4j API jar that is at least at >> the 2.6 version? >> >> Ralph >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
