+1
Ralph
> On Apr 25, 2024, at 5:00 AM, Christian Grobmeier wrote:
>
> Hi,
>
> By accident, I stumbled across this issue today:
> https://github.com/apache/logging-log4cxx/issues/370
>
> We think we should use the standard websites across all our repo
the artifact and include
> it as it in Log4j 3.0.0?
>
> Piotr
>
> [1] https://github.com/apache/logging-log4j2/issues/2395
I’ve delayed answering because I can’t make up my mind. I am still thinking
about this.
Ralph
> On Feb 12, 2024, at 12:58 PM, Piotr P. Karwasz
> wrote:
>
> Hi Volkan,
>
>> On Mon, 12 Feb 2024 at 20:30, Volkan Yazıcı wrote:
>> `StatusLogger` can be configured in following ways:
>>
>> 1.
Yes, add the missing method.
We use these methods A LOT. I suspect we are not alone.
Ralph
> On Feb 13, 2024, at 3:17 AM, Piotr P. Karwasz wrote:
>
> Hi all,
>
> Our Logger interface contains 11 traceEntry/traceExit methods and 4
> deprecated entry/exit methods. As far as I have seen, only
That is kind of my point. Anyone who logs an object that behaves this way is
asking for trouble. It really sounds like an esoteric edge case to me. I don’t
view this as a Log4J problem as the error wouldn’t even have Log4J in the stack
trace.
Ralph
> On Jan 25, 2024, at 9:52 PM, Gary Gregory
If this is a runtime dependency then I am against using it in Log4J api and
core.
Ralph
> On Jan 2, 2024, at 3:17 AM, Piotr P. Karwasz wrote:
>
> Hi all,
>
> Matt made an interesting proposal to use JSpecify nullability
> annotations in Log4j:
>
> https://github.c
I agree with everything Remko said plus these extra comments.
Throwing is a convenience method to standardize the output when an application
will be throwing an exception. That, of course, means it isn’t a required
method. I doubt it is used very much. Of course, catching is its companion but
In my experience they never get fixed. To be honest, when I was doing the
releases I would have these failures investigated to determine if it was a
trait problem vs a problem in the code being released. If it was the latter I
would cancel the vote. The only time tests should be disabled is if
s I know the 1.7.x branch is
> not supported any more by Ceki; I know this contains some support for
> structured events from `slf4j-ext` 1.7.25 that is not present in
> `log4j-slfj42-impl`, but I suppose this is no longer needed.
>
> There are some changes we are waiting for
>
If you want separate logging config files in an EJB environment using JNDI is
pretty much required. The same would be true for any properties needed in the
configuration.
In any case, despite Piotr saying this is a majority vote, it is not. I will
veto any attempt to remove JNDI components
We really don’t have much choice. With JPMS you really need to use
ServiceLoader to locate things like plugins across modules. Using a s file like
spring.factories doesn’t really help anyway. You wouldn’t want to force users
to hand create the entries in that file and so would use annotations
I am ok with 1 and 2, but not 3. Doing that means older releases web sites are
no longer available. Just because the latest includes release notes for all
versions doesn’t mean it fully documents what was in prior releases. However, I
am not surprised you are suggesting this as I posted in an
+1
Fix the staging site. Defer talk about anything else until that is done.
Ralph
> On Oct 22, 2023, at 5:05 PM, Christian Grobmeier wrote:
>
>
>
>> On Sun, Oct 22, 2023, at 21:54, Volkan Yazıcı wrote:
>> It has been a long thread and I want to capture the result: *there are no
>>
the loss of log4j-jmx-gui. Is log4j-jmx-gui 2.20.0
>>> compatible with log4j 2.21.0?
>>
>> Yes, it is, but there should be a `log4j-jmx-gui` version 2.21.0 out there:
>>
>> https://github.com/apache/logging-log4j-jmx-gui/releases/tag/rel%2F2.21.0
>>
>> I am no
Sure
Ralph
> On Oct 10, 2023, at 2:05 AM, Piotr P. Karwasz wrote:
>
> Hi all,
>
> Since Log4j Audit will not be archived, could someone update its
> dependencies? Dependabot has lots of security alerts about it:
>
> https://github.com/apache/logging-log4j-a
rio, I use Docker.
>
> As an example, for the privacy website to check:
> docker run --rm -p 4000:4000 --mount type=bind,src=$PWD,dst=/root/build
> --mount type=volume,dst=/root/build/node_modules -it
> apache/privacy_apache_org serve --watch --incremental
>
> There
Spring cloud config client is NOT part of Spring Boot 3. It adds a watcher for
the config file. I never created a PR to add it to Sping Cloud Config.
Ralph
> On Sep 9, 2023, at 11:24 AM, Piotr P. Karwasz wrote:
>
> Hi Gary,
>
>> On Sat, 9 Sept 2023 at 18:07, Gary Gregory wrote:
>>
>>
I agree with everything Gary says on this one. Furthermore, I still believe
some of these should move to their own repo.
Ralph
> On Sep 9, 2023, at 6:51 AM, Gary Gregory wrote:
>
> Hi All.
>
>> * raise the Java requirements in 3.x to Java 17.
> +1 fine w/ me. FWIW, my day job is migrating
t
> https://dist.apache.org/repos/dist/dev/logging such reviewed don't
> have to dig through folders.
>
> Gary
>
>> On Mon, Sep 4, 2023 at 3:33 PM Volkan Yazıcı wrote:
>>
>> This is a vote to release the Apache Logging Parent 1.10.0.
>>
>&g
1692821047719209>) that
>> users ask questions in GitHub Issues, we point them to the mailing list,
>> and they disappear. See this ticket
>> <https://github.com/apache/logging-log4j2/issues/1722> for an example.
>> Consequently, Matt proposed using GitHub Discussions. Rob
We need to look into this now that scoped variables are present.
Ralph
> On Mar 28, 2023, at 5:46 AM, David Delabassee
> wrote:
>
> Welcome to the latest OpenJDK Quality Outreach update!
>
> Last week was busy as we released both Java 20 and JavaFX 20. To celebrate
> the launch, we hosted
I would be comfortable with this if it is moved to its own repo and released
first, then removed from the Log4J repo. I am not comfortable with “we can do
it someday if we want to” unless we are dropping support for it.
Ralph
> On Mar 20, 2023, at 3:36 AM, Volkan Yazıcı wrote:
>
> [TLDR:
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:
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
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
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
&
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:
>>
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
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
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
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
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
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
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
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
gt; 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
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:
> h
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 instr
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
>>
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 existing
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
ires 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 cons
am 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
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:
: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
RA/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
>>
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>
>> tick
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
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
. 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 under the apache o
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
: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
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.
>
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
>
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
ava 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 on
>
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
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 reading some
>> > <https:
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
: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
>> 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) and push
en. 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/
>> 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
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)
f 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/pull/63 -- i
t 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 (:
>>>>>
>>>>>
>>>>>
>>>>> Thanks for all the help (:
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
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
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
re stored in the private
>>> repos of
>>> >> >> logging
>>> >> >> >>>>> pmc. Most members of the pmc should be in the set of recipients
>>> >> with
>>> >> >> their
>>> >> >&g
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
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-54 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
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,
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-61 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-54 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
loning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-24 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --versi
loning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-51 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --versi
sitory
Fetching without tags
> git rev-parse --is-inside-work-tree # timeout=10
> git config remote.origin.url https://github.com/apache/logging-log4net.git #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using
sitory
Fetching without tags
> git rev-parse --is-inside-work-tree # timeout=10
> git config remote.origin.url https://github.com/apache/logging-log4net.git #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using
sitory
Fetching without tags
> git rev-parse --is-inside-work-tree # timeout=10
> git config remote.origin.url https://github.com/apache/logging-log4net.git #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using
loning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-59 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --versi
loning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-54 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --versi
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-60 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
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
10
> git config remote.origin.url https://github.com/apache/logging-log4net.git #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> git fetch --no-tags --
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-59 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
g 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 seem to be a fool's errand
>>> to open a 3
ed 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 Apache wrote:
>>
>> No
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
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-54 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-43 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-53 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-51 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-24 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-56 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
ub.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-57 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
> g
loning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
> git init f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-57 #
> timeout=10
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --versi
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
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 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,
1 - 100 of 1485 matches
Mail list logo
