[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414474#comment-16414474
]
Cassandra Targett commented on SOLR-7887:
-----------------------------------------
bq. The website https://logging.apache.org/log4j/2.x/ has 2.x and not 2.11
Heh, there's a trick!
This might break ivy-versions.properties, but one option is to change the
versions to something like this:
{code}
org.log4j.major.version = 2
org.log4j.minor.version = 11.0
org.apache.logging.log4j.version =
${org.log4j.major.version}.${org.log4j.minor.version}
{code}
Then you could change the line in the Ref Guide to something like:
{code}
Solr uses http://logging.apache.org/log4j/{ivy-log4j-version}.x/[Log4J] for
logging which is configured using `server/resources/log4j2.xml`.
{code}
(This would put the right link to docs, but omit the version in user display
for the link.)
The goal of SOLR-12118 was to get links to 3rd party documentation in line with
versions being used in Solr without per-release manual review/intervention. If,
however, doing it is a burden or breaks other things, we can remove the
variable from the URL and only use it in the display text for the link, like
this:
{code}
Solr uses http://logging.apache.org/log4j/[Log4J {ivy-log4j-version}] for
logging which is configured using `server/resources/log4j2.xml`.
{code}
It would be OK if we dropped the minor version in that case, and it preserves
the spirit of the variable. Users going to that link would have the information
they need to know (from the link they just clicked on) the version of docs to
look at should the Log4J community choose to publish their docs by more
complete version again. If you think this is preferable, [~varunthacker], it's
fine with me to change it this way instead.
> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
> Key: SOLR-7887
> URL: https://issues.apache.org/jira/browse/SOLR-7887
> Project: Solr
> Issue Type: Task
> Reporter: Shawn Heisey
> Assignee: Erick Erickson
> Priority: Major
> Fix For: 7.4
>
> Attachments: SOLR-7887-WIP.patch, SOLR-7887-eoe-review.patch,
> SOLR-7887-eoe-review.patch, SOLR-7887-followup_1.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final
> logging destination, so the admin UI has a log watcher that actually uses
> log4j and java.util.logging classes. That will need to be extended to add
> log4j2. I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j. Figuring out exactly which
> jars need to be in the lib/ext directory will take some research.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
