[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413111#comment-16413111
]
Erick Erickson commented on SOLR-7887:
--------------------------------------
I think it's ready!
[[email protected]]: I had to change a bit of ivy-versions.properties,
/log4j/log4j is never referenced in the places like solr/core/ivy.xml after
this patch and precommit failed. Specifically where you broke out the
"org.log4j.major.version = 1.2". I made a trivial change but just in case it
affects the javadoc builds I thought I'd call it out.
- Upgraded to Log4J 2.11 rather than 2.10 since it's been released.
- This requires LMAX-disruptor, which is licensed under Apache 2.0, but what
should go in the disruptor-NOTICES.txt file? It's just a zero-byte file now.
There is a disruptor-LICENSE-ASL.txt file with the full license.
- jar-checksums, precommit and test targets all completed successfully, even
after clearing out my ivy cache and doing a clean-jars
I'll commit this later today so we can start getting some mileage on it.
> 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
> Affects Versions: 5.2.1
> Reporter: Shawn Heisey
> Assignee: Erick Erickson
> Priority: Major
> Attachments: SOLR-7887-WIP.patch, SOLR-7887-eoe-review.patch,
> SOLR-7887-eoe-review.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]
