[ https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-1836. --------------------------------- Resolution: Fixed Fix Version/s: 2.8.2 > API Version is incorrect > ------------------------ > > Key: LOG4J2-1836 > URL: https://issues.apache.org/jira/browse/LOG4J2-1836 > Project: Log4j 2 > Issue Type: Bug > Components: API, Core > Affects Versions: 2.6, 2.6.1, 2.6.2, 2.7, 2.8, 2.8.1 > Reporter: Ralph Goers > Fix For: 2.8.2 > > > ProviderUtil in Log4j API is supposed to list the versions of the API that > are all compatible with each other from a binding point of view. These > versions are not supposed to be modified with each Log4j release but only > when a change to the API is made so that implementations can know whether > they are compatible with the API. > Likewise, each implemenation (such as Log4j core) is supposed to declare what > version of the API it requires. Again, this is not implemented with each > release but only when core is modified to require changes in the API. > The API changed significantly in releases prior to 2.6 but these values were > never modified. Since 2.6 very little has changed in the API. > To fix this issue the API needs to say the only compatible version is 2.6 and > log4j-core must declare that it requires version 2.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org