[ https://issues.apache.org/jira/browse/LOG4J2-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma reassigned LOG4J2-1591: ----------------------------------- Assignee: Remko Popma > New method on LifeCycle interface breaks binary compatibility > --------------------------------------------------------------- > > Key: LOG4J2-1591 > URL: https://issues.apache.org/jira/browse/LOG4J2-1591 > Project: Log4j 2 > Issue Type: Bug > Reporter: Remko Popma > Assignee: Remko Popma > Priority: Blocker > Fix For: 2.7 > > > https://issues.apache.org/jira/browse/LOG4J2-1539 introduced method > {{stop(long, TimeUnit)}}. > LifeCycle is a top level interface extended by Appender, Configuration, > Filter and Filterable. This change will break implementations that don't > extend our abstract classes. > We should pull the new method out into a new {{LifeCycle2 extends LifeCycle}} > interface. Our abstract super classes would all implement the new interface. > In places where we are given a LifeCycle object and want to invoke the new > method we first need to check that it implements LifeCycle2. If it doesn't, > our code should probably call the existing stop() method so that existing > custom user code continues to work. > -- 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