You cannot replace. We always must support dots. But some people have asked for
'/' as well.
Sent from my iPad
> On Aug 13, 2017, at 8:38 AM, Dominik Psenner wrote:
>
> Yes
>
>> On 13 Aug 2017 5:13 p.m., "Gary Gregory" wrote:
>>
>> You are talking about replacing $ with dot in the getLogger
I guess it was changed from getPid() to pid() after 156. I will have to see if
Jenkins has a newer release.
Sent from my iPad
> On Aug 20, 2017, at 7:51 PM, Apache Jenkins Server
> wrote:
>
> See
> <https://builds.apache.org/job/Log4j%202.x/3005/display/redirect?page=cha
I am thinking about doing the Log4J 2.9.1 release at the end of the week as
there are a couple of bugs I'd like published by the time Java 9 is released.
Ralph
I created a Log4J-appserver module and added the Tomcat support there. I took a
look at jetty and it supports Log4J by routing it through slf4j. I'd like to
change that but I am not too familiar with the internals of jetty so that might
take a bit.
Ralph
> On Sep 7, 2017, at 4:47 AM, Mikael St
mment there but as it is closed I would like to ring a bell here as well.
> In Apache CloudStack, we have the the long overdue need to move to log4j2 so
> I gave a stab at it and one of the obstackles is a thing called SshHelper. It
> gets instantiated with a logger from a test class but t
From your configuration the limit is 5 per rollover interval. You are
specifying an interval of one day. Are you getting more than 5 per day?
Ralph
> On Nov 16, 2017, at 1:44 AM, Seweryn Habdank-Wojewodzki (JIRA)
> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/LOG4J2-2121?page=
t; I'll look at the checksums and the site next.
>
> Gary, could you run another clean build?
> The error messages look strange: I cannot see any difference between the
> expected and the actual result in the error output...
>
>
>
> Apache Maven 3.3.9 (bb52d8502b132
The Logging api only allows you to log a single event at a time so it doesn’t
make sense for an appender to have a method that accepts multiple events since
it can’t happen. That said, appenders can queue the events and send them
downstream in batches. I believe some of the appenders do that now
Log4j 2 does not lock when calling appenders so you will not have the deadlock
you show.
Ralph
> On Jan 17, 2018, at 4:28 AM, Vikas Mangla wrote:
>
>
>
> Just to update, the kind of deadlocks we observe in the application as
> attached.
>
>
>
> From: Vikas Mangla
> Sent: Wednesda
I haven’t looked yet but make sure the new module dependencies are added to
Log4J-distribution.
Ralph
> On Jan 29, 2018, at 6:55 AM, Gary Gregory wrote:
>
> On Sun, Jan 28, 2018 at 7:38 PM, Gary Gregory
> wrote:
>
>>
>>
>> On Sun, Jan 28, 2018 at 2:25 PM, Ralph Goers
>> wrote:
>>
>>> I s
wrote:
>>
>> I think it’s possible to search for a commit hash in IntelliJ, but here is a
>> github link:
>> https://github.com/apache/logging-log4j2/commit/21bc3aa3bf8d8a043459c6a58e774b82a617a058
>>
>> LOG4J2-2225 provide alias for SystemMillisClock so th
We are using the latest version of the clirr plugin.
Ralph
> On Mar 5, 2018, at 9:57 PM, Gary Gregory wrote:
>
> The site is using an old version of maven-site-plugin which in turns
> depends (IIRC) on a version of Apache BCEL that does not know what to do
> with Java 8 and/
But that does give me an idea. If there is a newer version of bcel I can
override the plugin to use it. I will try that tomorrow.
Ralph
> On Mar 5, 2018, at 11:12 PM, Apache wrote:
>
> We are using the latest version of the clirr plugin.
>
> Ralph
>
>> On Mar 5
But I would expect getContentType to return a mime type, not a charset.
Ralph
> On Mar 6, 2018, at 9:17 PM, Gary Gregory wrote:
>
>> On Tue, Mar 6, 2018 at 6:01 PM, Remko Popma wrote:
>>
>> Sorry, I don’t follow.
>> Why not get the appender’s layout and get the charset by calling
>> getCharse
Please do. Thanks!
Ralph
> On Mar 20, 2018, at 11:20 PM, Atle Tokle wrote:
>
> I made a fresh clone from master today, and looked into it myself.
> In CommandLineHelpTest.java all the tests that is failing is instanciating
> a Help class. In all cases it have an alternative constructor where yo
Obviously I didn’t see Remko’s reply before sending mine.
Ralph
> On Mar 21, 2018, at 4:57 AM, Apache wrote:
>
> Please do. Thanks!
>
> Ralph
>
>> On Mar 20, 2018, at 11:20 PM, Atle Tokle wrote:
>>
>> I made a fresh clone from master tod
e existing git-wip-us
>> infrastructure
>>>> to
>>>>>> the currently supported gitbox infrastructure that Infra advocates
>>> for
>>>>>> using nowadays. Using gitbox will allow our projects to integrate
>>>> better
>>>
Ok. I will take a look in the morning.
Sent from my iPad
> On Jun 10, 2018, at 12:23 AM, Remko Popma wrote:
>
> That is with
> C:\Users\remko\IdeaProjects\logging-log4j-audit-sample>mvn --version
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017
Oh. You don’t have the maven plugin. Since it hasn’t been released yet you will
have to build the Log4J audit project.
Sent from my iPad
> On Jun 10, 2018, at 12:23 AM, Remko Popma wrote:
>
> That is with
> C:\Users\remko\IdeaProjects\logging-log4j-audit-sample>mvn --version
helpful.
Ralph
> On Jun 10, 2018, at 1:36 AM, Apache wrote:
>
> Oh. You don’t have the maven plugin. Since it hasn’t been released yet you
> will have to build the Log4J audit project.
>
> Sent from my iPad
>
>> On Jun 10, 2018, at 12:23 AM, Remko Popma wrote:
>>
u say that’s accurate?
>
>> On Mon, Jun 11, 2018 at 00:54, Apache wrote:
>>
>> One thing I forgot to mention. Although Log4J audit doesn’t make use of
>> the product or category the catalog’s usefulness really comes into play
>> when you want to create a UI to query
gt;>>>
>>>> Ralph
>>>>
>>>>> On Jun 14, 2018, at 4:35 PM, Ralph Goers
>>>> wrote:
>>>>>
>>>>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
>>>> Mik
If you are familiar with Jenkins you should just be able to create one.
Ralph
> On May 7, 2019, at 12:53 AM, Andrei Ivanov wrote:
>
> Hi,
> I'm trying to see if there's a CI job defined for the Audit project.
>
> I'm looking at https://builds.apache.org/view/L/view/Logging/ and I don't
> see o
The code you highlight is there to include the throwable converter if one is
not specified. If you add your own throwable converter then handlesThrowable
will be true and that code won’t be run.
You can also hide the exception with %noex.
Under what circumstances do you want to hide the excepti
n Sat, Jun 22, 2019 at 12:24, Ralph Goers
>>> wrote:
>>>
>>>> Yes.
>>>>
>>>> Ralph
>>>>
>>>>> On Jun 22, 2019, at 9:54 AM, Gary Gregory
>>>> wrote:
>>>>>
>>>>> I would dro
Yes, that was a very interesting read and describes very well how JMH works.
Ralph
> On Jul 7, 2019, at 4:30 AM, Remko Popma wrote:
>
> This may be of interest:
> https://www.researchgate.net/publication/333825812_What's_Wrong_With_My_Benchmark_Results_Studying_Bad_Practices_in_JMH_Benchmarks
>
As I said, no one with commit privs should appear in the due-to. Ever. They
already appear in the by column and in git. It diminishes the thanks we give to
contributors to add ourselves, so I would request you please stop doing that,
frankly I am not sure why you started as I don’t recall seeing
final Exception e) {126
>if (e != null) {127
> LOGGER.error("Unable to write to Kafka in appender [" + getName() +
> "]", e);128}129 }130
>});131}132}133}
>
&
I thought you all might be interested in this -
https://www.ralphgoers.com/home/why-was-log4j-2-created. I plan to write a few
entries on what is new in Log4J.
Ralph
I have no plans to do this in master. One of the main goals of 3.0 is to be
fully modularized. This is just one part of that.
Ralph
> On Mar 8, 2020, at 5:26 AM, Gary Gregory wrote:
>
> Is this worthy doing in 2.0? In 3 we can do whatever we want IMO.
>
> Gary
>
>> On Sat, Mar 7, 2020, 23:2
Rats. Substitute “no plans” with “only plans”.
Ralph
> On Mar 8, 2020, at 6:31 AM, Apache wrote:
>
> I have no plans to do this in master. One of the main goals of 3.0 is to be
> fully modularized. This is just one part of that.
>
> Ralph
>
>> On Mar 8, 202
I started testing this. It doesn’t handle daylight savings at all and some of
the tests make no sense. I’m rewriting it using java.time and implementing
better tests.
Ralph
> On Mar 8, 2020, at 11:19 AM, Ralph Goers wrote:
>
> Is anyone else having problems with TimeFilterTest in core today?
No one is ever happy moving a project to dormant status. But it is unfair to
users to let them think the project is being maintained when the reality is
quite different than that.
The main issue that needs to be overcome is getting a release out. The ASF has
some requirements around releases
ough it's all MS based via
> TFS and MSTest).
>
> Having said that, it sounds like Mr McColl has a strong interest in keeping
> it alive, and I'd be happy to offer assistance in any way he finds
> beneficial.
>
> Thanks.
>
>> On Mon, Apr 6, 2020 at 12:50 AM A
ortunately, this would suggest that forking and publishing under a
>>> different package name is probably the best idea. There are, as noted
>>> before, 34 stagnated pull requests currently at GitHub, many of which
>>> haven't seen any attention since 2018. It would se
Feel free to merge it. I will test it there when I can.
Ralph
> On May 22, 2020, at 4:50 AM, Volkan Yazıcı wrote:
>
> Hey Ralph,
>
> Here is my status update:
>
> -~- Benchmarks -~-
>
> I have removed the benchmarks results. It takes ~8h for a complete run
> and I don't want to repeat that
Yes, please do.
Ralph
> On Jul 22, 2020, at 6:22 AM, Volkan Yazıcı wrote:
>
> Ralph, I am fine with the current state of the plugin. I don't intend to
> have further improvements in the short-term regarding KeyValuePair
> enhancements and/or escape character handling. If you are okay with it,
Don’t convert whole files. You only need to convert where there is an existing
document that is xdoc that needs to be updated.
Ralph
> On Aug 19, 2020, at 11:53 PM, Volkan Yazıcı wrote:
>
> Hello,
>
> I have started cherry-picking JsonTemplateLayout from master into
> release-2.x. There I wa
account are stored in the private
>>> repos of
>>> >> >> logging
>>> >> >> >>>>> pmc. Most members of the pmc should be in the set of recipients
>>> >> with
>>> >> >> their
>>> >> &
I do not believe the site has been updated to reflect the release. I looked
into it but couldn’t figure out how to build the site.
Ralph
> On Aug 24, 2020, at 6:38 AM, Dominik Psenner wrote:
>
> Hi
>
> People noticed that the release notes of 2.0.9 are missing while they
> should be document
No, you are not expected to do anything else. While anyone can be the release
manager, typically I have been doing them. They take a fair amount of time so I
typically start them on a weekend when I have enough time.
Ralph
> On Aug 27, 2020, at 6:14 AM, Volkan Yazıcı wrote:
>
> Would anybod
I will take care of the main logging site. It currently uses the ASF CMS but we
have to get off of it so there isn’t much point in you having to learn how to
deal with it.
Ralph
> On Aug 28, 2020, at 12:26 AM, Davyd McColl wrote:
>
> Hi all
>
> I've been trying to update content for http://
release! I’m sure you’ve just made a lot of
>>>> developers happy. :D
>>>>
>>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>>
>>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>>
>>>>>
>>>>>
>>>
d thing. Some of these changes are
>> required to resolve issues for netstandard2.0 users who have upgraded to
>> 2.0.9. Community member NicholasNoise put in a lot of work on this.
>>
>> If it helps, the original PR is here:
>> https://github.com/apache/logging-log4net/
It is good that you are letting others know your plans. As the only formal
Log4Net committer you are free to do whatever works for you. Hopefully that
won’t remain the case forever.
Ralph
> On Sep 10, 2020, at 2:17 AM, Davyd McColl wrote:
>
> Hi all
>
> I'd like to start (at some point) cl
>> On Thu, Aug 27, 2020 at 3:55 PM Apache wrote:
>>
>> No, you are not expected to do anything else. While anyone can be the
>> release manager, typically I have been doing them. They take a fair amount
>> of time so I typically start them on a weekend when I have enou
You can
>> always just run it from the command line although that requires installing
>> JBake on your computer.
>
>> The documentation for log4cxx is already maintained in its own repo. I moved
>> it a couple of weeks ago. It is now at
>> https://github.com/apache/
gt;
>> On Sep 22, 2020, at 11:21 PM, Davyd McColl wrote:
>>
>> Thanks all; I've completed the release as far as I can (Ralph, please push
>> the relevant artifacts from
>> https://github.com/apache/logging-log4net/releases/tag/rel%2F2.0.11 the last
>> mile
:08 AM, Gary Gregory wrote:
>
> Very odd indeed, the public (non-snapshot) repository is full of snapshots:
>
> https://repository.apache.org/content/groups/public/org/apache/logging/log4j/log4j-core/
>
> Gary
>
>> On Sun, Nov 1, 2020, 00:51 Ralph Goers wrote:
&
I will take care of 1 & 2 and will check your Jira permissions. The next
release will be 2.14.1 unless new enhancements are added.
Our general policy has been to mark issues resolved and ask users to close them
when they verify the fix. It would be nice if Jira would automatically close
them af
>> > and I'm not failing the same thing anymore.
>> >
>> > But I'm still getting errors, this time it is failing some unit tests from
>> > the surefire plugin. I tried to fix it but I couldn't.
>> >
>> >
>> >
>> > From rea
I just go periodically and search for “Log4j2” newest.
Ralph
> On Mar 31, 2021, at 4:32 AM, Volkan Yazıcı wrote:
>
> Thanks! Replied.
>
> Ralph, how do you track SO questions? I am watching log4j and log4j2 tags,
> though I don't see any notifications. In particular, I was expecting to get
>
java allocation
>> instrumenter wasn’t working and it had to be upgraded too.
>>>
>>> Ralph
>>>
>>>> On Mar 29, 2021, at 3:51 PM, Matt Sicker wrote:
>>>>
>>>> I’ll make sure to look more closely at it this week. Nice work o
Yazıcı
>> wrote:
>>>
>>> Hello,
>>>
>>> I have created a GitHub PR (#476)
>>> <https://github.com/apache/logging-log4j2/pull/476> addressing
>> LOG4J2-3004
>>> JsonTemplateLayout plugin support
>>> <https://issue
Yes, I saw the update when I woke up in the middle of the night. We use Spring
a lot at Nextiva so making the two interoperate nicely is important to me.
Ralph
> On Apr 6, 2021, at 6:23 AM, Volkan Yazıcı wrote:
>
> For those who don't know yet, Spring Boot considers switching from Logback
> t
Can we not require a Jenkinsfile in each project that sets properties to
control the behavior?
Ralph
> On Apr 6, 2021, at 6:45 AM, Matt Sicker wrote:
>
> Oops, good point. I need to make the version selection a little more
> sophisticated. Probably a branch or something for the shared lib.
>
:14 PM, Volkan Yazıcı
>> wrote:
>>>>
>>>> As subject hints, I am not able to run tests in IDEA anymore after Java
>> 11
>>>> upgrade. I have deleted all IDEA related files and issued a clean Maven
>>>> build:
>>>>
>>&g
That would be exactly right. I would create a TimeFilter that is very much like
the DynamicThresholdFilter but instead of using an MDC key it woul use a time
frame.
This would be interesting as it could be implemented to either check the time
in the event for every request or it could create a
fluence ... not a git repo.
>> And I guess I can help with all the getting started, once we've decided
>> on a plan.
>>
>> Chris
>>
>>> On 07.07.21 09:52, Davyd McColl wrote:
>>> Hi Ralph
>>>
>>> I can't create a repo unde
I don’t think anyone passing an escape sequence expects it to show up as a
string. So I would be good with your proposed solution. That method should be
part of core so we can modify all Layouts to use it.
Ralph
> On Sep 13, 2021, at 12:29 AM, Volkan Yazıcı wrote:
>
> I had addressed this is
We could include it in Log4J. Does master work out of the box?
Ralph
> On Oct 13, 2021, at 12:23 AM, Volkan Yazıcı wrote:
>
>
> I have done something really nasty in the release-2.x branch to fix
> benchmarks.jar generated by log4j-perf. Since a picture is worth a thousand
> words, I am sha
l-lists.html>.
>> For instance, the module name, transformer name, documentation changes,
>> etc.
>> This will give others an opportunity to share their feedback and remarks.
>> Then simply create a JIRA <https://issues.apache.org/jira/projects/LOG4J2>
>> ticket and
GitHub+Pages
>>>>>>>
>>>>>>> On Fri, Oct 15, 2021 at 6:35 PM Ralph Goers
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I don’t really understand this. When I was migrating the web site from
>>
:14 AM, Volkan Yazıcı wrote:
>
> In its current state, all Logging Services projects (log4j, log4jcxx,
> log4net, etc.) dump their websites to a single repository:
> https://github.com/apache/logging-log4j-site If I need to publish
> continuous benchmark results of logging-log4j2 rep
It sounds to me like you want to create a new type of plugin similar to
PatternConerters. I am curious as to what your filter does. Is it something
that would be useful to others so that we would be interested in including it?
Ralph
> On Oct 21, 2021, at 6:07 AM, Adwait Kumar Singh
> wrote:
>
trying to
> finish up some work on
> Apache Flume so it can get a new release and I need to do some other work
> here as we
> are overdue for a release.
>
> Ralph
>
>> On Oct 21, 2021, at 11:28 AM, Adwait Kumar Singh
>> wrote:
>>
>> The problem I am s
requires knowing now the changes plugin passes data to Doxia and what
>> Doxia is going to do to
>> render it. If you look at
>> https://github.com/apache/maven-changes-plugin/blob/master/src/main/java/org/apache/maven/plugins/changes/ChangesReportGenerator.java
>> in the
https://github.com/apache/log4j was read-only. The new repo is not.
Ralph
> On Dec 22, 2021, at 11:34 PM, Ralph Goers wrote:
>
> I have cloned the read-only log4j repo to
> https://github.com/apache/logging-log4j1.
>
> I have followed the build instructions and had to
mir Sitnikov
> wrote:
>
> Leo>Instead of or in addition to some of those fixes
>
> I would suggest the following (in case you wonder, I might volunteer to do
> ALL of that, so don't assume I just sit and tell others how things should
> be done):
> 1. Use the exis
Thanks Leo. I was using Java 8 with maven 3 in a Linux VM. I don’t think maven
3 runs on Java 6.
Ralph
> On Dec 23, 2021, at 5:11 AM, Leo Simons wrote:
>
> On Thu, 23 Dec 2021 at 12:39, Ralph Goers
> wrote:
>
>> It is still the middle of the night for me so I won’t do anything for
>> severa
tch the branch name of our other repos?
>
> Gary
>
>> On Thu, Dec 23, 2021 at 1:34 AM Ralph Goers
>> wrote:
>>
>> I have cloned the read-only log4j repo to
>> https://github.com/apache/logging-log4j1.
>>
>> I have followed the build instructions
es harder by requesting Java
>> 1.6
>> looks like an overkill.
>>
>> I think there's no way to install Java 1.6 on modern macOS.
>
> Correct. I would suggest Docker, if there is a way to install it there.
>
> Here is some more installation instructions:
&
wrote:
>>
>>>
>>> On Thu, Dec 23, 2021, at 14:05, Gary Gregory wrote:
>>>> One of the difficulties was likely related to building the Windows DLLs
>>>> for
>>>> using the Windows Event Log Appender (
>>>>
>>>
>> htt
of `changes.xml`?
>
> -- Forwarded message -
> From: Kristjan Esperanto
> Date: Sun, Dec 19, 2021 at 12:08 PM
> Subject: [apache/logging-log4j2] Add Link to Release History (PR #642)
> To: apache/logging-log4j2
> Cc: Subscribed
>
>
> It's a mi
I should have added that you should not delete it.
Ralph
> On Dec 24, 2021, at 7:00 AM, Apache wrote:
>
> The release notes file is generated for every release.
>
> Ralph
>
>> On Dec 24, 2021, at 6:20 AM, Volkan Yazıcı wrote:
>>
>> Is this file still r
Infra has a mailing list and a slack channel.
Ralph
> On Dec 26, 2021, at 6:00 AM, Carter Kozak wrote:
>
> I filed an infra ticket for this, but it hasn’t been picked up yet:
> https://issues.apache.org/jira/browse/INFRA-22641
> Might be worth emailing someone? Otherwise they may be busy with
540e769d98c42d018fa1bc1b8
> Author: Carter Kozak
> AuthorDate: Sat Dec 25 11:48:20 2021 -0500
>
>LOG4J2-3289: Fix log4j-to-slf4j re-interpolation of formatted message data
> ---
> .../java/org/apache/logging/slf4j/SLF4JLogger.java | 28 ++
> .../java/org/apache/l
Please don’t forget to apply this to the master branch.
Ralph
> On Dec 26, 2021, at 6:31 AM, ggreg...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> ggregory pushed a commit to branch release-2.x
> in repository https://gitbox.apache.org/repos/asf
The answer is - it depends. Although we might consider using the properties
proposal I made in master many of the lookups should default to being enabled
or enabled under a condition. For example, the spring lookup only works when
spring boot is present. It would be stupid for it not to be enabl
Wrong list
Ralph
> On Apr 2, 2022, at 5:08 AM, Gary Gregory wrote:
>
> We just released our release tool, Apache Commons Release Plugin Version
> 1.8.0:
> An Apache Maven Mojo for Apache Commons Release tasks.
>
> Historical list of changes:
> https://commons.a
Lol. Ok An app running in Java 11. That changes nothing. We can certainly make
some incompatible changes but as we have previously discussed some of the
things you removed will have to be reverted.
Making Log4J 3 not backward compatible would be a disaster.
Ralph
> On Apr 18, 2022, at 5:07 PM,
It is implemented on master.
Ralph
> On May 30, 2022, at 2:27 AM, Volkan Yazıcı wrote:
>
> Mind somebody sharing the last state? Is it implemented, if so how and on
> which branch(es)? Is it reverted? If so, totally or partially?
>
>> On Sun, May 29, 2022 at 9:53 AM Ralph Goers
>> wrote:
>>
vider::getInstance which
>>>> can be implemented using Injector in Log4j Core. The general utility class
>>>> for working with this provider is available as an internal (util3) class
>>>> in LoggingSystem. Test fixture helper classes have also been updated to
&
l package and
> export it to other Log4j modules. That makes sense.
>
> And LoggingSystem probably doesn’t need a Lazy instance of itself, right.
>
> —
> Matt Sicker
>
>> On Oct 31, 2022, at 20:58, Apache wrote:
>>
>>
>>
>> See be
Consistent
Ralph
> On Nov 16, 2022, at 5:23 PM, Matt Sicker wrote:
>
> Is this a consistent failure or random?
>
>> On Nov 16, 2022, at 3:42 PM, Ralph Goers wrote:
>>
>> I haven’t run a build in a while and looking at the recent commits I am not
>> sure what is causing this, but some chang
False is the default so I left it alone. It also means it is specified in less
places.
Ralph
> On Dec 30, 2022, at 5:26 AM, Gary Gregory wrote:
>
> Should that setting be flipped such that a Maven module ask to be Javadoc'd?
>
> Gary
>
>> On Fri, Dec 30, 2022, 07:23 Volkan Yazıcı wrote:
>>
Nevermind. I think Gavin fixed it.
I imagine Jenkins has to be modified as well.
> On Apr 11, 2017, at 11:50 PM, Ralph Goers wrote:
>
> Matt,
>
> It seems Jira is still configured to send to the individual lists. I don’t
> seem to have rights to change that. I have asked Gavin to fix that in
We have to do something. I am about 3/4 of the way creating java9 modules and I
am not happy with core at all. Far too many classes have to be exported as you
can only name packages, not classes.
I think all the configuration stuff will need to stay in core, which means the
optional dependency
Gary, you are missing the point. We are not "going" to java 9. We will be
providing support for it. There was nothing we had to do to support java 8, but
there are changes that must be made, like using StackWalker and being
modularized, for Log4J to be usable by everyone who moves to java 9. If
You could try using java 9
Sent from my iPad
> On Apr 26, 2017, at 2:20 AM, Mikael Ståldal wrote:
>
> Now I cannot build the project in IntelliJ IDEA anymore. It complains that
> lambda expressions are not supported in Java 7 in StackWalkerStackLocator.
>
> Any suggestions?
>
> On Fri, Apr 21
-log4net.git
>>
>> github integration is enabled for this repository and therefore it is
>> mirrored to github here:
>>
>> https://github.com/apache/logging-log4net
>>
>> Please do not commit to the svn repository anymore! That repository is about
I read that previously but if Log4J implements modules I don't see how the
nodal appenders or flume appender can work.
I also got a reply to my query about referencing dependencies that are not yet
modularized and the recommendation is to only use the manifest entry and not
have a module-info.j
n Tue, May 9, 2017 at 12:24 AM, Apache wrote:
>>
>> I read that previously but if Log4J implements modules I don't see how the
>> nodal appenders or flume appender can work.
>>
>> I also got a reply to my query about referencing dependencies that are not
>&
Yes, although we could fully modularize the API right away.
Ralph
> On May 9, 2017, at 12:51 AM, Gary Gregory wrote:
>
>> On Tue, May 9, 2017 at 12:34 AM, Apache wrote:
>>
>> Technically you are considered modularized just by adding a manifest entry
>> providin
It will require that modules that have Log4J plugins declare the package
containing the plugins as "open" to Log4J. Apparently we will also have to
call Module.addReads() to be able to access the module.
Ralph
Sent from my iPad
> On May 10, 2017, at 2:40 AM, Mikael Ståldal wrote:
>
> As fa
l does not protect
> against this as far as I can see. I have put in some protection in
> KafkaAppender:
> https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaAppender.java#L133
>
> Without th
The reason managers were split from the appender sis because appender are
recreated during reconfiguration while managers are reused.
Ralph
> On Jun 7, 2017, at 1:11 AM, Gary Gregory wrote:
>
> Hi All:
>
> I've completed all the clean ups I think were needed in the
> GenericMapMessageSimple b
og4j:log4j-api:jar:2.9-SNAPSHOT :
> Classes found in the wrong directory:
> {META-INF/versions/9/org/apache/logging/log4j/util/
> StackLocator.class=org.apache.logging.log4j.util.StackLocator}
> [ERROR] Error(s) found in manifest configuration
> [INFO]
> ---
(default) @ log4j-api ---
> [ERROR] Manifest org.apache.logging.log4j:log4j-api:jar:2.9-SNAPSHOT :
> Classes found in the wrong directory:
> {META-INF/versions/9/org/apache/logging/log4j/util/
> StackLocator.class=org.apache.logging.log4j.util.StackLocator}
> [ERROR] Error(s) fou
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.
1 - 100 of 500 matches
Mail list logo
