[
https://issues.apache.org/jira/browse/LOG4J2-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-1596.
-------------------------------
Resolution: Won't Fix
For the next release I would like to set up something like REVAPI (LOG4J2-1576)
so that the build breaks when binary compatibility is broken.
We then either fix the code so it is binary compatible again, or we add
exceptions/filters for the cases where this is not a problem. This last bit can
also serve as documentation for users.
> Additional params on public methods break binary compatibility
> ---------------------------------------------------------------
>
> Key: LOG4J2-1596
> URL: https://issues.apache.org/jira/browse/LOG4J2-1596
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Remko Popma
> Priority: Blocker
> Fix For: 2.7
>
>
> See LOG4J2-1576 for a full list.
> These can all be resolved by keeping the old method with an implementation
> that delegates to the new method with a reasonable default value for the new
> parameter.
> * FileManager.getFileManager
> * RandomAccessFileManager.getFileManager
> * RollingFileManager.getFileManager
> * RollingRandomAccessFileManager.getFileManager
> * IdlePurgePolicy::createPurgePolicy
> *
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
