This area of the code is used by most operations and there are frequently
NPE's encountered in it. We have typically tried to solve those problems
at their cause instead of adding the null check. I just ran into one
yesterday when I was adding the Lock support. It turned out to be because
JavaHL was sending just a file name in the notification instead of the
absolute path to the file, and the code is expecting a full file object.
In this case it was a JavaHL bug, but once we were aware of it we can work
So the best thing would be to try to diagnose what might be unique about
your situation that would cause this null when others do not get it.
Another recent example, fixed in 0.9.29, happened after commit on Linux
boxes. Problem turned out to be some code that was supposed to find the
common root between the files and was returning null.
Hopefully you can find the cause and let us know.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Thu May 5 10:17:56 2005