Does the log4j-android module shade in log4j-api or something? If not, we still have the same exact initial problem of Java 9 classes being in the jar.
On 10 July 2017 at 17:08, Remko Popma <[email protected]> wrote: > I think both Gary and myself had the same misunderstanding about > log4j-api-android. I didn't realize it contains a bridge/adapter to the > Android logging implementation until you mentioned it. > > Would `log4j-api-android-impl` be a better name? > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Jul 11, 2017, at 5:51, Ralph Goers <[email protected]> > wrote: > > > > > >> On Jul 10, 2017, at 1:31 PM, Gary Gregory <[email protected]> > wrote: > >> > >> A log4j-api-android jar is a terrible idea and confusing: Wouldn't the > only > >> difference with log4j-api be that the Java 9 optimization be absent? If > so, > >> that's a LOT of code duplication for no gain IMO. The KISS solution is a > >> log4j-api-java9 jar with the Java 9-specific code, right now, just the > one > >> class. > > > > I would suggest you look at log4j-api-android on the android branch. It > should provide a working implementation of the API on Android. > > > > The answer to your question is, “No”. It routes the Log4j API to the > android logger, which IMO is the ONLY sensible thing you can do on Android. > > > > Ralph > -- Matt Sicker <[email protected]>
