You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2017/11/04 17:09:02 UTC

[jira] [Commented] (LOG4J2-2099) API changes report for Log4j API snapshot

    [ https://issues.apache.org/jira/browse/LOG4J2-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239104#comment-16239104 ] 

Ralph Goers commented on LOG4J2-2099:
-------------------------------------

Thanks. Is there something we are supposed to do with this Jira issue? Are you requesting we add a link to the web site or something?

FWIW, the graph only tells part of the story. The Log4j API has several classes that have to be public but are noted with Javadoc comments. Generally, those are the only classes where you may see binary incompatibilities and, as the graph shows, that doesn't happen often.

> API changes report for Log4j API snapshot
> -----------------------------------------
>
>                 Key: LOG4J2-2099
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2099
>             Project: Log4j 2
>          Issue Type: Documentation
>            Reporter: Andrey Ponomarenko
>         Attachments: log4j-api-1.png, log4j-api-2.png
>
>
> Hi,
> I'd like to share report on API changes and backward compatibility for the Log4j API library: https://abi-laboratory.pro/java/tracker/timeline/log4j-api/
> BC — binary compatibility
> SC — source compatibility
> The report is generated according to the article https://wiki.eclipse.org/Evolving_Java-based_APIs_2 by the https://github.com/lvc/japi-tracker tool.
> The analysis for the latest snapshot version of the library from https://repository.apache.org/content/repositories/snapshots/org/apache/logging/log4j/log4j-api/ is included to the report.
> Hope it will be helpful for users and maintainers of the library.
> Thank you.
> !log4j-api-2.png|API symbols timeline!
> !log4j-api-1.png|API changes review!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)