These steps worked for me (cwilper) as of 2019/05/20. You don't need to deploy Solr this way...I'm just documenting what worked for me today.
This is the parent directory of your dspace and solr installs.
For example, if you will be deploying your dspace install under $HOME/Work/dspace/community-7/dspace
, then
BASEDIR
should be set as follows:
BASEDIR=$HOME/Work/dspace/community-7
Note: Here we use Solr 7.3.1 because that is the exact version of the client libraries currently used by DSpace. A newer 7.x might work, but I wouldn't advise using Solr 8+ -- the automatic core upgrade version check in the ant deploy script is not compatible with it.
cd $BASEDIR
wget http://archive.apache.org/dist/lucene/solr/7.3.1/solr-7.3.1.tgz
tar -xvf solr-7.3.1.tgz
ln -s solr-7.3.1 solr
ln -s ../../../dspace/solr solr/server/solr/dspace
Build and deploy from this branch, which has a couple necessary fixes that aren't in master
yet:
https://github.com/atmire/DSpace/tree/DS-3695-solr-fixes
Make sure the solr url is correct in your deployed local.cfg
If you're upgrading from a DSpace 6 database, run $BASEDIR/dspace/bin/dspace database migrate ignored
now.
$BASEDIR/solr/bin/solr start -p $SOLR_PORT
...with SOLR_PORT matching what's in your local.cfg
Use your normal way of starting DSpace. Then run:
$BASEDIR/dspace/bin/dspace index-discovery -b