Please review and provide feedback on
https://cwiki.apache.org/confluence/display/LOGGING/Properties+Enhancement.
Note that some of the major goals of 3.0 are:
* Fully support the Java Platform Module System by having all relevant jars
contain a module-info.java class.
* In support of JPMS, hav
One person's EOL is another person's open source business model ! (RHEL
subscriptions are not cheap!)
Anyway, quick FYI - I noticed Atlassian has rev'd log4j-1.2.17 fifteen
times ! Might be some good patches in there. They do publish the
"sources.jar":
https://packages.atlassian.com/3rdparty
End-Of-Life means End-Of-Life and that is the end of the story.
If someone keeps patching an End-Of-Life component, how should downstream
understand when they should update their product?
The answer to this question is the technical definition of End-Of-Life.
Upgrade, migrate, rewrite, throw awa
https://github.com/albfernandez/log4j/ is one fork I found that
published a fixed copy on Maven Central. Confluent also publishes a
forked copy, though I don't know where their source code is (package
names are renamed as it's mainly used by old versions of Confluent's
hosted services, so it's poss
my comment is below:
On Fri, 7 Jan 2022 at 14:23, Christian Grobmeier
wrote:
> Hello,
>
> On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote:
> > As for infringing on the log4j trademark, I will rename the repo to
> > something else, for example "re4j".
> >
> > As mentioned in my previous message,
The Log4cxx JIRA is pretty clean at the moment - Thorsten went through
it a few months ago so there's not much (if anything) to do there.
-Robert Middetlon
On Fri, Jan 7, 2022 at 11:47 AM Matt Sicker wrote:
>
> I think this is a great idea. I'm sure we can find some dupes and link
> some other i
I think this is a great idea. I'm sure we can find some dupes and link
some other issues into existing epics along with other housekeeping.
On Fri, Jan 7, 2022 at 8:26 AM Ralph Goers wrote:
>
> You mean Log4j 2 Jira issues. Yes, please. At least once a month. Possibly
> twice so
> we can get th
You mean Log4j 2 Jira issues. Yes, please. At least once a month. Possibly
twice so
we can get through the backlog. If Log4cxx and Log4Net want to do something
similar
I’m sure a few of us would be happy to help even though we may not know the
code.
Ralph
> On Jan 7, 2022, at 5:48 AM, Gary
Hello,
On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote:
> As for infringing on the log4j trademark, I will rename the repo to
> something else, for example "re4j".
>
> As mentioned in my previous message, if the ASF decides to integrate
> "re4j" as log4j 1.x, the door is open.
Thanks. You did n
We have mentioned in the past going through Jiras in a meeting once in a
while. Does anyone still have to appetite for this review? Should we
schedule it?
Gary
Hi all,
Where can we record this decision? In a text file in the repo? Wiki? Both?
Gary
On Fri, Jan 7, 2022, 05:22 Volkan Yazıcı wrote:
> Hello,
>
> This is the result of the vote introducing the process that enforces
> CVE submissions[1] and their content to be first subject to voting by
> me
Hello,
This is the result of the vote introducing the process that enforces
CVE submissions[1] and their content to be first subject to voting by
means of "lazy approval"[2] using the (private)
`secur...@logging.apache.org` mailing list:
6x +1 (accepting the process), all binding
2x +0 (abstainin
+1 (with lazy approval)
On Mon, Jan 3, 2022 at 12:59 PM Volkan Yazıcı wrote:
> Hello,
>
> As discussed earlier[1], this is a vote to introduce the process that
> enforces CVE submissions and their content should be first subject to
> voting using the (private) `secur...@logging.apache.org` maili
13 matches
Mail list logo
