Re: [Log4j] 2.9 release and Java 9

On 9 July 2017 at 18:32, Ralph Goers wrote: > > > > On Jul 9, 2017, at 1:29 PM, Matt Sicker wrote: > > > > Suppose we have an Android-specific api jar. Then when an Android > developer > > gets log4j-api transitively, what now? I don't see normal

Re: [Log4j] 2.9 release and Java 9

I created a log4j-api-android module on branch “android”. It contains an AndroidLogger that logs to android.util.Log. I have not built it on Android or tested it. Can you give it a whirl? Ralph > On Jul 9, 2017, at 5:11 PM, Gary Gregory wrote: > > On Jul 9, 2017

Re: [Log4j] 2.9 release and Java 9

> On Jul 9, 2017, at 11:45 AM, Gary Gregory wrote: > > On Sun, Jul 9, 2017 at 10:49 AM, Ralph Goers > wrote: > >> When I investigated logging on android I came to the conclusion that the >> only usable logging that can be done in android is

Re: [Log4j] 2.9 release and Java 9

> On Jul 9, 2017, at 1:29 PM, Matt Sicker wrote: > > Suppose we have an Android-specific api jar. Then when an Android developer > gets log4j-api transitively, what now? I don't see normal libraries using > log4j-api-android or something instead of the standard one. This

Mentor Support Log4J2

I would like to help contribute, is there anyone out there that can help a newbie? I've helped correct some things in the cms webpage but I would like to get experience doing more than correcting typos. Can someone shadow me? Thanks in advance! kennethpaulmcfarl...@gmail.com

[GitHub] logging-log4j2 pull request #40: LOG4J2-1511-fix-dynamic-threshold-filter-to...

Github user surukuntu closed the pull request at: https://github.com/apache/logging-log4j2/pull/40 --- 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

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079786#comment-16079786 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user jvz commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Thanks, we got notification of the ICLA. --- 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

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079763#comment-16079763 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on the issue:

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079768#comment-16079768 ] Gary Gregory commented on LOG4J2-1921: -- ATM, the 2.9-SNAPSHOT log4j-api jar includes a Java 9

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user leventov commented on the issue: https://github.com/apache/logging-log4j2/pull/87 @remkop I have not competed this PR yet, there are a few more things need to be done. I will try to complete PR in the next weekend. Also I've just sent ICLA to secret...@apache.org --- If

Re: [Log4j] 2.9 release and Java 9

On Jul 9, 2017 16:59, "Ralph Goers" wrote: > On Jul 9, 2017, at 2:42 PM, Gary Gregory wrote: > > On Sun, Jul 9, 2017 at 1:29 PM, Matt Sicker wrote: > >> Suppose we have an Android-specific api jar. Then when an Android

Re: [Log4j] 2.9 release and Java 9

> On Jul 9, 2017, at 2:42 PM, Gary Gregory wrote: > > On Sun, Jul 9, 2017 at 1:29 PM, Matt Sicker wrote: > >> Suppose we have an Android-specific api jar. Then when an Android developer >> gets log4j-api transitively, what now? I don't see normal

Re: [Log4j] 2.9 release and Java 9

On Sun, Jul 9, 2017 at 1:29 PM, Matt Sicker wrote: > Suppose we have an Android-specific api jar. Then when an Android developer > gets log4j-api transitively, what now? I don't see normal libraries using > log4j-api-android or something instead of the standard one. > I am not

Re: [Log4j] 2.9 release and Java 9

Suppose we have an Android-specific api jar. Then when an Android developer gets log4j-api transitively, what now? I don't see normal libraries using log4j-api-android or something instead of the standard one. On 9 July 2017 at 13:45, Gary Gregory wrote: > On Sun, Jul 9,

Re: Build failed in Jenkins: log4net-trunk-tests #112

I broke the runtests target when I refactored the tests to make them run in the pipeline. This probably means that the test project fetches nunit framework with a different filename than it is shipped with the zip file we download. It was probably a bad idea to download the dependency manually. We

Re: [Log4j] 2.9 release and Java 9

On Sun, Jul 9, 2017 at 10:49 AM, Ralph Goers wrote: > When I investigated logging on android I came to the conclusion that the > only usable logging that can be done in android is with the implementation > that Google provides. I have no problem creating a Log4J jar

Build failed in Jenkins: log4net-trunk-tests #111

See -- Started by upstream project "log4net-trunk-build" build number 241 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building

Build failed in Jenkins: log4net-trunk-tests #110

See Changes: [dpsenner] builder-netstandard: attempt to run groupadd and useradd in the stage [dpsenner] Revert "builder-netstandard: attempt to run groupadd and useradd in the [dpsenner] build-netstandard:

Re: [Log4j] 2.9 release and Java 9

When I investigated logging on android I came to the conclusion that the only usable logging that can be done in android is with the implementation that Google provides. I have no problem creating a Log4J jar for android but I am not willing to not support Java 9 to do it. Ralph > On Jul 9,

Re: [Log4j] 2.9 release and Java 9

But there is a file system on Android... On Jul 9, 2017 10:15, "Matt Sicker" wrote: > It does seem that the problem is indeed only with log4j-api. While an > Android developer might have some setup to get logging working during > development, that's a separate scenario from

Re: [Log4j] 2.9 release and Java 9

It does seem that the problem is indeed only with log4j-api. While an Android developer might have some setup to get logging working during development, that's a separate scenario from simply allowing libraries that depend on log4j-api to still work in Android. I do think that log4j-core could be

Re: [log4net] ci pipeline status update

> > dotnet test inside of the directory is what I've done so far. >> >> Stefan >> > > I'm adding dotnet test into the jenkinsfile. We'll see what happens. :-) > This is the outcome. So something works, but I see no tests and a strange warning. {quote}

Re: [Log4j] 2.9 release and Java 9

Assume that I am an Android developer. I don't know about Log4j, and I don't care much about logging. I don't care about Java 9. In my Android app I want to use a Java library, which claims to support Android. When I include a dependency to that library in my Gradle build, the build breaks

Re: [log4net] ci pipeline status update

2017-07-09 18:22 GMT+02:00 Stefan Bodewig : > On 2017-07-09, Dominik Psenner wrote: > > > I finally managed to build the netstandard assemblies in our jenkins > > pipeline. It was a tough task and the solution feels like a hack, but it > > works. See: > > >

Re: [log4net] ci pipeline status update

On 2017-07-09, Dominik Psenner wrote: > I finally managed to build the netstandard assemblies in our jenkins > pipeline. It was a tough task and the solution feels like a hack, but it > works. See: > https://builds.apache.org/job/logging-log4net/job/develop/ > The problem was that dotnet always

Re: [log4net] ci pipeline status update

Ok, the hack has its price. The uid is not always the same and therefore builds may randomly fail: https://builds.apache.org/job/logging-log4net/view/change-requests/job/PR-8/9/console This is a call for help. Does anyone have a good idea how this issue can be solved for good? 2017-07-09 17:37

[log4net] ci pipeline status update

Hi, I finally managed to build the netstandard assemblies in our jenkins pipeline. It was a tough task and the solution feels like a hack, but it works. See: https://builds.apache.org/job/logging-log4net/job/develop/ The problem was that dotnet always attempts to find and store dependent

Build failed in Jenkins: log4net-trunk-tests #108

See Changes: [dpsenner] Jenkinsfile: run mono-2.0 tests and record test results [dpsenner] Jenkinsfile: fixed typo [dpsenner] Jenkinsfile: record git log -1 into the package [dpsenner] Tests: download and

[jira] [Commented] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079635#comment-16079635 ] Paul K commented on LOG4J2-1967: if hard code the property value in the xml, the exception does not

Re: [Log4j] 2.9 release and Java 9

What does it mean to support android? You cannot log to a file system and many of our out of the box appender make no sense on a phone. What does having the API work on android mean without an implementation? We have never officially supported android and have just gotten our first Jura issue

[jira] [Updated] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1694: --- Affects Version/s: 2.8 2.8.1 2.8.2 > Allow to

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079609#comment-16079609 ] Mikael Ståldal commented on LOG4J2-1694: [~vy] I have now recreated the LOG4J2-1694 branch. I

Re: [Log4j] 2.9 release and Java 9

No matter what we think about it, many other Java libraries want to be compatible with Android (even though that's not the main target). Some of them also do logging, today often with Log4j 1, SLF4J or commons-logging. If we want them to migrate to Log4j 2 API, then it is important that

Re: [Log4j] 2.9 release and Java 9

* When I said "Java 9 has been on the roadmap" I meant the Log4j 2 roadmap. On Sun, Jul 9, 2017 at 9:15 PM, Remko Popma wrote: > Not sure I agree. Our interest in Android is a very recent thing. We've > done some work with LOG4J2-1926 >

Re: [Log4j] 2.9 release and Java 9

Not sure I agree. Our interest in Android is a very recent thing. We've done some work with LOG4J2-1926 , we are still discovering new work and I suspect we will keep discovering new issues as we start to take an in-depth look. If anything, let's

[Log4j] 2.9 release and Java 9

As far as I understand, Java 9 will be released September 21. Now we plan to release Log4j 2.9 before the end of July. Given the problems that Java 9 causes, at least for Android, I suggest that we de-scope the Java 9 specific stuff (StackLocator) from the 2.9 release. It should be possible