Log4j has run into a few of them. The OSGi bind tool has some issues although the latest release fixes some of them. Android’s tools have problems with any jar that contains anything Java 9 related. We have created issues against both of these.
Ralph > On Mar 8, 2018, at 6:33 AM, Gilles <gil...@harfang.homelinux.org> wrote: > > Hello. > > On Wed, 7 Mar 2018 22:21:44 +0000, Stephen Colebourne wrote: >> On 7 March 2018 at 18:56, Ralph Goers <ralph.go...@dslextreme.com> wrote: >>> Actually, you really do need to use a multi-release jar to include a >>> module-info class file. Otherwise it may be sitting alongside of classes >>> compiled for an earlier java release and various tools will fail because of >>> it. >> >> Then those tools need fixing. >> >> Using multi-release jar files doesn't really help either, as other >> tools don't understand those. > > Would it be useful (and interesting as part of GSoC work) to > establish > (1) which tools requires fixing, > (2) prepare enhancement requests for the respective projects, > and in the meantime, adapt the "Commons" build (with a "JDK 9" > profile) > (3) to disable plugins that do not work yet, > (4) provide the option to generate a "multi-release" JAR (although > it would not be the deployed as part of the official release > process)? > > Regards, > Gilles > >> Stephen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
