Oh, then likely the problem is that your uberjar packing tool doesn’t know how
to (or maybe isn’t configured to?) include/merge/translate resources under
META-INF/services/. E.g. lucene/core module has SPI files there.
Info on the maven shade plugin’s configuration for this stuff is here here:
Thanks
I am not sure if Steve's suggestion was the right solution. Even when I
did not have explicitly defined the dependency on lucene, I can see in
the packaged jar it still contains org.apache.lucene.
What solved my problem is to not pack a single jar but use a folder of
individual jars.
We also faced same issue when we were running embedded solr 6.1 server.
Actually I faced the same in our integration environment after deploying
project. Solr 6.1 is using http client 4.4.1 which I think embedded solr
server is looking for. I think when solr core is getting loaded then old
http cl
solr-core[1] and solr-solrj[2] POMs have parent POM solr-parent[3], which in
turn has parent POM lucene-solr-grandparent[4], which has a
section that specifies dependency versions & exclusions
*for all direct dependencies*.
The intent is for all Lucene/Solr’s internal dependencies to be manage
Hi, I am using Solr, Solrj 6.1, and Maven to manage my project. I use
maven to build a jar-with-dependency and run a java program pointing its
classpath to this jar. However I keep getting errors even when I just
try to create an instance of EmbeddedSolrServer:
*/code/
*String
