[ 
https://issues.apache.org/jira/browse/LOG4J2-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Remko Popma updated LOG4J2-1596:
--------------------------------
    Description: 
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
* 


  was:
See LOG4J2-15xx 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
* 



> 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

Reply via email to