Perhaps we should revert Java 9 features and defer them to 3.0.0 where we require Java 8 minimum as it is. It leaves a distinct legacy splitting point.
On Tue, Feb 20, 2018 at 20:48, Gary Gregory <[email protected]> wrote: > Hi All: > > https://issues.apache.org/jira/browse/LOG4J2-2173 is yet another example > of > a jar (ours) breaking an application as it attempts to support Java 9. It > really does not matter that code is not supposed to look at class files in > a jar here or there (I'm looking at you META-INF); or that they cannot deal > with module-info files that have this or that byte code. It breaks stuff. > It's a mess. > > MR jars break Android tools. MR jars broke my company's internal build > tooling which I had to frantically fix. It's just a constant and recurrent > theme. > > What can we do? > > How about dropping the MR jaring (a horrible design with this META_INF > business IMO)? > > Java 9 bits and extra functionality can be provided in a separate JAR and > maybe a service loader. > > Then there is the fact that Java 9 and 10 are DOA since there is no LTS. > Another mess. > > Thoughts? > Gary > -- Matt Sicker <[email protected]>
