Yeah, it would be nice to tell Maven/Nexus to use a different artifact when building for Android but the best we can do is to document it well on the web site.
Ralph > On Jul 12, 2017, at 12:49 PM, Mikael Ståldal <[email protected]> wrote: > > It looks fine. > > The problem is that Android developers who get a transitive dependency to > log4j-api now explicitly have to exclude it, and include log4j-api-android > instead. > > It is not hard to do, but how do we reach out to those Android developers who > might not even know what Log4j is (and don't care much about logging)? > > > On 2017-07-10 22:49, Ralph Goers wrote: >>> On Jul 10, 2017, at 1:48 PM, Ralph Goers <[email protected]> wrote: >>> >>> >>>> On Jul 10, 2017, at 1:25 PM, Mikael Ståldal <[email protected]> wrote: >>>> >>>> Exactly. It would be better with a log4j-api that works on Android and >>>> then a log4j-android module as an alternative to log4j-core. >>>> >>> >>> >>> I would suggest you look at log4j-api-android. It should provide a working >>> implementation of the API on Android. I really don’t see the point of doing >>> much more than this on a phone. >> This is on the android branch. >>> >>> Ralph > >
