Re: Playing with Android...

Still not simpler that log4j-api-java9... On Sat, Jul 8, 2017 at 10:02 PM, Matt Sicker wrote: > That's what I'm getting at with the plugin. I'm sure log4j won't be the > first or last common jar to have multi-version support. I wonder if this > situation is any better than the Scala one where ea

Re: Playing with Android...

This does not work: packagingOptions { exclude 'META-INF/DEPENDENCIES' exclude 'META-INF/LICENSE' exclude 'META-INF/versions/9/**' Gary On Sat, Jul 8, 2017 at 9:35 PM, Ralph Goers wrote: > NOTHING should be looking for class files under the META-INF directory. > Both the Maven Bun

Re: [log4j] Doc improvement proposal

Makes sense to me. That could've been a historical issue because the JMS appender used to be two plugins (queue and topic). On 8 July 2017 at 23:15, Gary Gregory wrote: > Hi All, > > In the docs, we talk about the "JMSAppender" but nowhere except for XML > examples do we mention that the configu

Re: Playing with Android...

That's what I'm getting at with the plugin. I'm sure log4j won't be the first or last common jar to have multi-version support. I wonder if this situation is any better than the Scala one where each major version has its own separate jar. I think the worst case scenario could be an android classif

Re: Playing with Android...

NOTHING should be looking for class files under the META-INF directory. Both the Maven Bundle plugin and now, it seems, Android have this problem. We get around this for OSGi by running the plugin before the Java 9 class (there is only 1 now) is added to the Jar. Can we do the same with Android

Re: Playing with Android...

I’m not in favor of delivering Java 9 support as a separate jar. What we have now is exactly the way Oracle expects libraries to implement it. Ralph > On Jul 8, 2017, at 7:26 PM, Gary Gregory wrote: > > I say we keep it simple: Deliver log4j-api-java9 as an add-on to log4j-api > instead of bei

[log4j] Doc improvement proposal

Hi All, In the docs, we talk about the "JMSAppender" but nowhere except for XML examples do we mention that the configuration element name is actually "JMS" and not "JMSAppender". I'm going to replace "JMSAppender" with "JMS Appender" in the docs to make that point. Feel free to update other appe

Re: Playing with Android...

On Sat, Jul 8, 2017 at 7:47 PM, Matt Sicker wrote: > Seems simpler to fix the Gradle plugin(s) for Android honestly. > How can changing plugins (I'm not using the work "fix" here) any easier? It sure would take a lot longer... and it's something we have no control over... Gary > > On 8 July 20

Re: Playing with Android...

Seems simpler to fix the Gradle plugin(s) for Android honestly. On 8 July 2017 at 21:26, Gary Gregory wrote: > I say we keep it simple: Deliver log4j-api-java9 as an add-on to log4j-api > instead of being clever with log4j-api embedding Java 9 classes a la > Titanic. > > Thoughts? > > Gary > > O

Re: Playing with Android...

I say we keep it simple: Deliver log4j-api-java9 as an add-on to log4j-api instead of being clever with log4j-api embedding Java 9 classes a la Titanic. Thoughts? Gary On Sat, Jul 8, 2017 at 7:10 PM, Gary Gregory wrote: > I do not think that is how Android development works. The .class files a

Re: Playing with Android...

Java 9 is turning into the Titanic in Java's history, and Android is just one iceberg on its route... Gary On Sat, Jul 8, 2017 at 7:10 PM, Gary Gregory wrote: > I do not think that is how Android development works. The .class files are > converted to .dex files from what I can tell, a different

Re: Playing with Android...

I do not think that is how Android development works. The .class files are converted to .dex files from what I can tell, a different byte code format used by both Dalvik (discontinued) and ART. Gary On Sat, Jul 8, 2017 at 6:15 PM, Apache wrote: > Is it trying to process the class files generate

Re: Playing with Android...

Is it trying to process the class files generated by java? I thought Android compiled Java source. If it is looking at class files then it needs to ignore everything under META-INF Sent from my iPad > On Jul 8, 2017, at 5:58 PM, Gary Gregory wrote: > > We are worst off with our 2.9-SNAPSHOT,

Re: Playing with Android...

The Log4J-API compile does not have any dependency on java 9 Sent from my iPad > On Jul 8, 2017, at 5:58 PM, Gary Gregory wrote: > > We are worst off with our 2.9-SNAPSHOT, I can't even build an app using > only log4j-api: > > AGPBI: {"kind":"error","text":"Error converting bytecode to dex:\nC

Re: Playing with Android...

It already is. Sent from my iPad > On Jul 8, 2017, at 5:58 PM, Gary Gregory wrote: > > We are worst off with our 2.9-SNAPSHOT, I can't even build an app using > only log4j-api: > > AGPBI: {"kind":"error","text":"Error converting bytecode to dex:\nCause: > Dex cannot parse version 53 byte code.

Re: Playing with Android...

We are worst off with our 2.9-SNAPSHOT, I can't even build an app using only log4j-api: AGPBI: {"kind":"error","text":"Error converting bytecode to dex:\nCause: Dex cannot parse version 53 byte code.\nThis is caused by library dependencies that have been compiled using Java 8 or above.\nIf you are

Re: Playing with Android...

If you've got some instructions on how to even get an Android project up and running, getting some test code to play with would certainly help. Long ago when I tried debugging some Android issues with Log4j, I couldn't even get that far. :/ On 8 July 2017 at 17:31, Gary Gregory wrote: > A quick

Re: Playing with Android...

A quick follow up to note that with 2.8.2, using log4j-api does not cause problems but then adding log4j-core causes the app to fail to start. So I definitively see an Android epic for 2.10. Maybe this is when we want to split up log4j-core. Gary On Sat, Jul 8, 2017 at 3:20 PM, Gary Gregory wrot

Playing with Android...

So here I am with my family our of town on a weekend, and I thought I'd give Log4j on Android a try. The first thing I run into is: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':Application:transformResourcesWithMergeJavaResForDebug'. > com.android.build

[jira] [Resolved] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1661. Resolution: Fixed Fix Version/s: 11.0 Marking as resolved since this is in Git maste

[jira] [Resolved] (LOG4J2-1690) Scala wrapper for Context map

[ https://issues.apache.org/jira/browse/LOG4J2-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1690. Resolution: Fixed Fix Version/s: 11.0 Marking as resolved since this is in Git maste

[jira] [Closed] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1969. -- > TcpSocketServer does not replace any “{}” in message > --

[jira] [Commented] (LOG4J2-969) Refactor SyslogAppender so that Layout is a Plugin element

[ https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079289#comment-16079289 ] ASF GitHub Bot commented on LOG4J2-969: --- Github user asfgit closed the pull request

[GitHub] logging-log4j2 pull request #46: add configurable syslog layout

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/46 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] logging-log4j2 pull request #45: Duplicate Code refactoring

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/45 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] logging-log4j2 issue #45: Duplicate Code refactoring

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/45 Thanks @prabh27 , applying your patch. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[jira] [Commented] (LOG4J2-969) Refactor SyslogAppender so that Layout is a Plugin element

[ https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079284#comment-16079284 ] ASF GitHub Bot commented on LOG4J2-969: --- Github user garydgregory commented on the i

[GitHub] logging-log4j2 issue #46: add configurable syslog layout

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/46 Sure, since https://issues.apache.org/jira/browse/LOG4J2-969 is closed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] logging-log4j2 issue #46: add configurable syslog layout

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/46 Can this PR be closed @garydgregory ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this f

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079280#comment-16079280 ] ASF GitHub Bot commented on LOG4J2-1864: Github user mikaelstaldal commented on t

[GitHub] logging-log4j2 issue #62: (LOG4J2-1864) Support capped collection for MongoD...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/62 Ping @jvz --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes s

Re: [log4cxx] Release process releated questions

1. I think a PMC has to commit the key to the file. 4. All sounds reasonable to me. 5. Normally we'd stage artifacts on Nexus. However, as we're not putting C++ stuff on Maven Central, I don't think that's right. I found this svn repo that looks p

[jira] [Resolved] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1969. Resolution: Fixed Fix Version/s: 2.8 Seems to work in 2.8.x. > TcpSocketServer does

[jira] [Commented] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079192#comment-16079192 ] YU Chang commented on LOG4J2-1969: -- It works! Thank you for your helping! By the way, it

Re: [1/5] logging-log4j2 git commit: LOG4J2-1923 Allow having the stacktrace as a string in JSONLayout, XMLLayout and YAMLLayout

Since we have a parameter "includeStacktrace" already, I think it's appropriate to name this new one "stacktraceAsString". On 2017-07-07 22:52, Gary Gregory wrote: Nit: "stacktraceAsString" -> "stacktTaceAsString".

[jira] [Commented] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079181#comment-16079181 ] Mikael Ståldal commented on LOG4J2-1969: Can you add this command line argument w

[jira] [Commented] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079124#comment-16079124 ] YU Chang commented on LOG4J2-1969: -- I try version 2.8.2 again, and record the exception

[jira] [Commented] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079088#comment-16079088 ] YU Chang commented on LOG4J2-1969: -- It is not very convenient to change the version of

Re: [log4cxx] Release process releated questions

Guten Tag Matt Sicker, am Freitag, 7. Juli 2017 um 22:41 schrieben Sie: > 1. You should add it to the logging project's KEYS file. I think I was one > of the last keys added to the file. I don't have write access to dist/release. Should I ask someone for write access or is someone else committing

Re: Releasing 2.9

Updating the performance page with the items you mentioned is on my todo list but I doubt I'll be able to get to it in July or even August. Performance testing, analyzing the results, redoing after finding I measured the wrong thing:-) and finally doing a write up of the results took me several we