When tracking bugs due to invalid directories names for the FSDirectoryProvider, it could be nice if the logs did inform more on Hibernate Search behaviour, or help highlight some problem.
E.g., if the indexes already exist on disk, under windows vista, and we provide the directory name with erroneous trailing spaces in the configuration file : Hibernate Search run half well : the only problem is that it clears the old indexes on initializing the FSDirectoryProvider since it didn't find the directory with the trailing spaces. After that, it doesn't seem to mind the wrong directory name since it finds and uses the good one.
Is suppose we could expect Hibernate Search to tell that something is happening and why, in fact, without having to go in the code with the debugger to find that the trailing spaces are sometimes a problem and sometimes not.
(this improvement was asked for on