It does break binary compatibility, but since it's log4j-core (not api) we agreed that this is acceptable here.
The reason it's a separate super interface is that I plan to have other Encoder implementations (perhaps user-specified) for binary logging. The Jira may have more details: https://issues.apache.org/jira/browse/LOG4J2-1274 Sent from my iPhone > On 2016/04/13, at 5:30, Gary Gregory <[email protected]> wrote: > > Now that Layout extends Encoder and Encoder is new in 2.6, why not fold > Encoder in Layout? > > Doesn't Layout extending a new type (Encoder) break BC anyway? > > Gary > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
