exported lucene collections don't work on windows 10.

[kjdon]

Here is some stuff from an email that I wrote.

The library server (server.exe) needs to have Perl in its PATH variable to be able to search lucene collections.

On my computer, where Perl is not automatically in the PATH, for normal local library server: if I start server by double clicking in the gsdl folder, it can't find perl and searhcing lucene doesn't work. if I open a terminal, add perl to the path and run server.exe from there, it works. If I install greenstone from a binary release, and run it from the start menu, it works.

If I export a lucene collection, then copy it into an existing greenstone, it works (dependent on the above conditions).

But, If I try to run the server.exe from the exported collection folder (by double clicking OR from a terminal with perl in the path), it doesn't work. I have copied in the same server.exe from my other greenstone but it still doesn't work. This is strange.

I haven't tried this with a cd that is installed first - this gets server into the start menu. Would it work then??

[kjdon]

Michael Goodwin has been exporting collections to dvd using lucene. They worked fine with windows 7, but not with windows 10. On windows 10 searching doesn't work. He is using a nightly of 2.87.

We need to fix this for the next greenstone 2 release.