OSGi seems to use re-packaged versions of Log4j2 most of the time
anyways for some reason. See for example
https://ops4j1.jira.com/wiki/spaces/paxlogging/pages/499613746/Configuring+Log4J2
On Fri, Feb 18, 2022 at 9:24 AM Ralph Goers wrote:
>
> It occurs to me that options 1 & 2 may not work well
It occurs to me that options 1 & 2 may not work well with OSGi and possibly
JPMS.
JPMS will require that the module have a unique name. It would need a
module-info
that specifies it requires org.apache.log4j. But users of this jar would be
requesting
org.apache.log4j and the jar would have to
Thanks, Ceki. Although the Apache license certainly allows copying code
to anything it is against ASF policy to take code against their author’s
wishes.
That said, we have not incorporated anything into log4j-1.2-api that we believe
may have security issues and won’t until we resolve them. Eve
Ralph,
I would like to observe that Vlardimir's JDBCAppender contribution was
made outside Apache. While the code in question is licensed under the
ASL, it has not been contributed to the Apache Foundation. Unless the
foundations rules have changed, you cannot copy the changes without
Vladimir's
I'd be between options 1 and 2. I'm not a fan of duplicating the jar,
though publishing an empty redirect jar isn't ideal either. Given that
most of the intractable bugs in v1 were related to how log events are
processed which now go through the v2 system, this seems like a good
way to continue sup
> On Jan 27, 2022, at 11:41 AM, Vladimir Sitnikov
> wrote:
>
>> 1. It is an exact copy of log4j-1.2-api with the binary, source, and
> javadoc jars renamed to log4j:log4j.
>> 2. The pom.xml has a dependency on log4j-1.2-api and the jar file is empty.
>
> The options are bad as log4j-1.2-api
>1. It is an exact copy of log4j-1.2-api with the binary, source, and
javadoc jars renamed to log4j:log4j.
>2. The pom.xml has a dependency on log4j-1.2-api and the jar file is empty.
The options are bad as log4j-1.2-api misses several classes that are used a
lot in log4j 1.x deployments.
For inst
Log4j 2.17.2 is going to contain at least 3 dozen fixes or improvements to the
log4j 1.2
support. One of our PMC members has been actively working on migrating his
employer’s
applications from Log4j 1.x to log4j-1.2-api and has had great success. We have
also
had users experience issues and t
