I am not in favor of this. I was told that moving module-info.java into the META-INF/versions/9 directory is valid and will remedy some of these problems. I intend to do that prior to the next release.
Although I agree what Oracle did is a mess there are people who want this stuff. In fact, someone has reported that our support doesn’t go far enough. I am also aware that SLF4J is now modularized and Logback is pretty close as well, so we cannot possibly be the only source of problems. Ralph > On Feb 20, 2018, at 7:48 PM, Gary Gregory <garydgreg...@gmail.com> 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
