We can also get rid of the import.properties file at this point too since all of the path info is in the vufind_home var.
From: Andrew Nagy
Sent: Monday, March 31, 2008 3:30 PM
To: 'Wayne Graham'; VuFind-General; vufind-tech@...
Subject: RE: [VuFind-Tech] Bugs in 0.8
Wayne - can't we just also include the vufind_home var in the import.sh file as well. Since the vufind.sh script must be run before hand, the vufind_home var is set. This can make for a good check as well to make sure solr is running by checking to see if vufind_home is set.
From: vufind-tech-bounces@... [mailto:vufind-tech-bounces@...] On Behalf Of Wayne Graham
Sent: Thursday, March 27, 2008 4:39 PM
To: VuFind-General; vufind-tech@...
Subject: [VuFind-Tech] Bugs in 0.8
There are two rather major bugs that have surfaced in the 0.8 release that I wanted everyone to know about, along with the fixes.
First, as many of you have figured out, the import.sh script is in the root of the vufind folder and the import.properties file needs to be in the same folder. The easiest fix is to either move the import.properties file up, or the import.sh script into the import folder.
The second bug is also related to the import.sh script. The variable SOLR_DATA_DIR is not being set properly. I will be committing a fix to both the trunk and Vufind-0.8 branch shortly, but wanted to let folks know that if you've indexed in 0.8, your index has most likely gone to /index (in root). You can just move these files into your $SOLR_HOME/data/index.
In the mean time, here is the condensed fix with the import.sh script:
if [ -z "$SOLR_HOME" ]
echo "You need to set the SOLR_HOME environmental variable before running this script."
if [ "$SOLR_HOME" ]
java $INDEX_OPTIONS -jar import/import.jar