Re: SLF4J now requires Java 6

2017-12-03 Thread Ralph Goers
In theory… Ralph > On Dec 3, 2017, at 11:11 AM, Matt Sicker wrote: > > Plus the whole multi-version jars feature is super handy for a library like > Log4j which can add support for each new Java version while maintaining BC > with older Java releases without having to resort to reflection hacks

Re: SLF4J now requires Java 6

2017-12-03 Thread Matt Sicker
Plus the whole multi-version jars feature is super handy for a library like Log4j which can add support for each new Java version while maintaining BC with older Java releases without having to resort to reflection hacks and other dynamic loading. On 3 December 2017 at 07:00, Remko Popma wrote:

Re: SLF4J now requires Java 6

2017-12-03 Thread Remko Popma
From Java 9, interfaces can have private methods that can be called from interface default methods. This is to reduce duplicate code in default method implementations. > On Dec 3, 2017, at 20:44, Mikael Ståldal wrote: > >> On 2017-12-03 00:24, Matt Sicker wrote: >> It's too bad that Java 8

Re: SLF4J now requires Java 6

2017-12-03 Thread Mikael Ståldal
On 2017-12-03 00:24, Matt Sicker wrote: It's too bad that Java 8 and 9 added language features that would have been immensely useful for maintaining a backwards compatible API (default and private methods on interfaces), Did Java 9 add anything more than Java 8 for this?

Re: SLF4J now requires Java 6

2017-12-02 Thread Matt Sicker
Requiring Java 8 minimum would make more sense to start with for Core and the other modules. It's too bad that Java 8 and 9 added language features that would have been immensely useful for maintaining a backwards compatible API (default and private methods on interfaces), though I suppose that wil

SLF4J now requires Java 6

2017-12-02 Thread Ralph Goers
And here you are complaining we haven’t moved to Java 8 as the minimum... http://slf4j.42922.n3.nabble.com/qos-ch-slf4j-5f0078-slf4j-api-now-requires-Java-6-td4026870.html Ralph