Re: Log4j2 APIs on Android

2017-06-17 Thread Remko Popma
I did some work to get closer to making Log4j2 API work on Android. What remains is the dependency on the java.lang.management package in ThreadDumpMessage and ExtendedThreadInformation. (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 17, 2017, at 16:50, Mikael S

Re: Log4j2 APIs on Android

2017-06-17 Thread Mikael Ståldal
I think Oleg have a point in that log4j-api is a bit too heavy currently. I was maybe a mistake to put concrete implementations of Message and StringMap there. The problem is not primarily the size, but that the implementation classes drag in unwanted dependencies (like this RMI dependency).

Re: Log4j2 APIs on Android

2017-06-16 Thread Mikael Ståldal
I am not sure I like Remko's solution to remove the dependency on RMI MarshalledObject in SortedArrayStringMap. I am afraid that this implementation: private static Object unmarshall(byte[] data) throws IOException, ClassNotFoundException { ByteArrayInputStream bin = new ByteArray

Re: Log4j2 APIs on Android

2017-05-31 Thread Remko Popma
Oleg, thanks for the clarification. I originally thought you meant the JMX classes in log4j-core. I think we may be able to come up with a different solution to (LOG4J2-1226 ) that does not involve MarshalledObject in log4j-api. I created https:/

Re: Log4j2 APIs on Android

2017-05-31 Thread Oleg Kalnichevski
On Thu, 2017-06-01 at 01:18 +0900, Remko Popma wrote: > Oleg, > > Elements in the Log4j configuration can be instrumented with MBeans > to > allow remote inspection and modification of an application's logging > configuration. As Matt pointed out, this can be disabled. > > There is no dependency

Re: Log4j2 APIs on Android

2017-05-31 Thread Remko Popma
...that said, there is an effort underway to break up log4j-core into smaller modules with more explicit dependencies. In light of what you are saying it may make sense to break out the ` org.apache.logging.log4j.core.jmx` package into a separate module. User domain objects and exceptions are wrap

Re: Log4j2 APIs on Android

2017-05-31 Thread Remko Popma
Oleg, Elements in the Log4j configuration can be instrumented with MBeans to allow remote inspection and modification of an application's logging configuration. As Matt pointed out, this can be disabled. There is no dependency on RMI as far as I know. There is a log4j-jmx-gui client module that c

Re: Log4j2 APIs on Android

2017-05-31 Thread Matt Sicker
Those Message implementations correspond to a lot of basic functionality you'll find in other APIs like SLF4J, so I wouldn't consider it heavy. Besides, that's also one of the key differentiating features between log4j-api and slf4j-api, for example. As for RMI, the only strange use I know of is i

Re: Log4j2 APIs on Android

2017-05-31 Thread Oleg Kalnichevski
On Wed, 2017-05-31 at 09:30 -0500, Matt Sicker wrote: > The JMX stuff can be disabled, and there are some other similar > optional > dependencies we've had to create due to some previously reported > issues > with missing classes on Android. As for full compatibility, I don't > think > any of the m

Re: Log4j2 APIs on Android

2017-05-31 Thread Matt Sicker
The JMX stuff can be disabled, and there are some other similar optional dependencies we've had to create due to some previously reported issues with missing classes on Android. As for full compatibility, I don't think any of the main developers here have worked on that, but patches and other contr

Log4j2 APIs on Android

2017-05-31 Thread Oleg Kalnichevski
Folks, I did try to do a reasonable research on the matter prior to posting my question here, nevertheless, please do excuse me if I am asking something obvious or well documented somewhere (in a place I was unable to find). I read that people had been more or less successfully using Log4j2 2.3 o