[ 
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384967#comment-16384967
 ] 

Erick Erickson commented on SOLR-7887:
--------------------------------------

I somehow didn't include disruptor-NOTICE.txt in my patch, included now.

If you have precommit failures and the like, here's a problem I had:

log4j-1.2.17.jar (and a couple of others) are no longer necessary. However, if 
you've built Solr sometime, even if you switch branches, you'll have some 
leftover symlinks in the following 4 directories that log4j-1.2.17.jar (and 
others) points to in your ivy cache.... which may not exist. Precommit will 
fail if they're not presetn.

NOTE: I was being thorough and deleting my ivy cache to be sure we'd get 
everything properly, if I hadn't I wouldn't have this problem.

solr/core/lib/
solr/solr-ref-guide/lib/
solr/server/lib/ext/
solr/solrj/test-lib/

So I just removed everything in the 4 directories above and I'm back being able 
to run precommit.

NOTE: _compiling_ worked even with the symlinks pointing nowhere.




> 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: Varun Thacker
>            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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to