[jira] [Commented] (LOG4J2-1926) Remove dependency on MarshalledObject from log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032529#comment-16032529 ] Remko Popma commented on LOG4J2-1926: - [~olegk] you mentioned there were 2 dependenc

[jira] [Commented] (LOG4J2-1294) Update Kafka client from 0.9.0.0 to 0.9.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032377#comment-16032377 ] ASF subversion and git services commented on LOG4J2-1294: - Commit

[jira] [Closed] (LOG4J2-1924) The JMS Appender should use a JMS MapMessage for a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1924. Resolution: Fixed Fix Version/s: 2.9 In Git master. > The JMS Appender should use a JMS Map

[jira] [Commented] (LOG4J2-1294) Update Kafka client from 0.9.0.0 to 0.9.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032359#comment-16032359 ] ASF subversion and git services commented on LOG4J2-1294: - Commit

[jira] [Updated] (LOG4J2-1924) The JMS Appender should use a JMS MapMessage for a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1924: - Description: The JMS Appender should use a JMS {{javax.jms.MapMessage}} for a Log4j {{org.apache

Re: Chainsaw in git

The old git repo on Github is the mirror of the subversion repo. That repo should go away when the svn repo is deleted. Ralph > On May 31, 2017, at 6:54 PM, Robert Middleton wrote: > > I just noticed that there's already a chainsaw git repo on Github and > ASF git, I assume that anything done

[jira] [Updated] (LOG4J2-1924) The JMS Appender should use a JMS MapMessage for a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1924: - Description: The JMS Appender should use a JMS {{javax.jms.MapMessage}} for a Log4j {{org.apache

Re: Log4j2 APIs on Android

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:/

[jira] [Updated] (LOG4J2-1926) Remove dependency on MarshalledObject from log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1926: Description: (Remko: Paraphrasing discussion on the log4j dev mailing list. Please feel free to up

[jira] [Created] (LOG4J2-1926) Remove dependency on MarshalledObject from log4j-api

Remko Popma created LOG4J2-1926: --- Summary: Remove dependency on MarshalledObject from log4j-api Key: LOG4J2-1926 URL: https://issues.apache.org/jira/browse/LOG4J2-1926 Project: Log4j 2 Issue Ty

Re: Chainsaw in git

I just noticed that there's already a chainsaw git repo on Github and ASF git, I assume that anything done to it would be against the logging-chainsaw.git and not chainsaw.git. Is that correct? -Robert Middleton On Wed, May 31, 2017 at 3:14 AM, Gary Gregory wrote: > A new Jira project or a comp

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032289#comment-16032289 ] Ralph Goers commented on LOG4J2-1925: - OK, thanks. > Having log4j-core on the compil

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032288#comment-16032288 ] Trejkaz commented on LOG4J2-1925: - I created an annotation processor which does nothing a

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032252#comment-16032252 ] Ralph Goers edited comment on LOG4J2-1925 at 6/1/17 12:34 AM: -

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032252#comment-16032252 ] Ralph Goers edited comment on LOG4J2-1925 at 6/1/17 12:34 AM: -

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032252#comment-16032252 ] Ralph Goers commented on LOG4J2-1925: - My suggestion would be to create an annotation

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032248#comment-16032248 ] Trejkaz commented on LOG4J2-1925: - I'm pretty sure javadoc doesn't support parsing Englis

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032233#comment-16032233 ] Ralph Goers edited comment on LOG4J2-1925 at 6/1/17 12:16 AM: -

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032233#comment-16032233 ] Ralph Goers edited comment on LOG4J2-1925 at 6/1/17 12:15 AM: -

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032233#comment-16032233 ] Ralph Goers edited comment on LOG4J2-1925 at 6/1/17 12:03 AM: -

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032233#comment-16032233 ] Ralph Goers commented on LOG4J2-1925: - Log4j-core has an annotation processor that wi

[jira] [Created] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

Trejkaz created LOG4J2-1925: --- Summary: Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it Key: LOG4J2-1925 URL: https://issues.apache.org/jira/browse/LOG4J2-1925

[jira] [Created] (LOG4J2-1924) The JMS Appender should use a JMS MapMessage for a Log4j MapMessage

Gary Gregory created LOG4J2-1924: Summary: The JMS Appender should use a JMS MapMessage for a Log4j MapMessage Key: LOG4J2-1924 URL: https://issues.apache.org/jira/browse/LOG4J2-1924 Project: Log4j 2

Re: [Log4j] Java 9

It all seems like a lot of FUD in retrospect. So the upshot of all of this drama is that one 5-line method was added and that some implementation choices are going to graduate to be in the specification? Gary On Wed, May 31, 2017 at 11:16 AM, Ralph Goers wrote: > Thanks, I hadn’t seen that as I

Re: [Log4j] Java 9

Thanks, I hadn’t seen that as I don’t follow that list. I had read the conference call notes for the JPMS work he discussed. They are at http://mail.openjdk.java.net/pipermail/jpms-spec-experts/2017-May/thread.html .

[Log4j] Java 9

FYI: A 2 month delay proposed for #java9 http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-May/005864.html #java Gary -- Java Persistence with Hibernate, Second Edition

Re: Log4j2 APIs on Android

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

...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

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

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

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

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

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

Re: Chainsaw in git

A new Jira project or a component of LOG4J2? Gary On May 30, 2017 9:04 PM, "Ralph Goers" wrote: > The question was where does he file the bug? > > Ralph > > > On May 30, 2017, at 6:55 PM, Scott Deboy wrote: > > > > File a bug and it would get attention. > > > > Also: contributions welcome! > >