You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "ppkarwasz (via GitHub)" <gi...@apache.org> on 2024/12/27 19:28:12 UTC

Re: [I] [MS30] Fix API compatibility issues (logging-log4j2)

ppkarwasz commented on issue #1867:
URL: https://github.com/apache/logging-log4j2/issues/1867#issuecomment-2563972860

   Over the past year the BND Baseline plugin prevented breaking API changes many times, e.g.:
   
   - fe92961737ed3423763df6219e892b2d1a3ad49b
   - 9f576e137b569b600cd086dd7522bc879bf16ff7
   - f0e82d15e7f718059ecb4207c6f63396e3fb7421
   - 9565d4b301f6ea4e422a1f3af1a661566b3dec20
   - b8cb35fbb88baccdbde36f157a5ef737f2d6ed22
   
   The only currently known limitation of the BND Baseline check is the case of the multi-release modules (`log4j-api-java9` and `log4j-core-java9`), because only their Java 9 equivalents are tested for API compatibility. We briefly explored the idea of using BND's multi-release support (cf. apache/logging-parent#93), but we decided to disable it (cf. apache/logging-parent#96), since it introduces a lot of complexity to the built artifacts.
   I believe that commits like 945cbc886b9f78abdfa4e478babf242c5f7be199 should be enough for our use case.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org