The problem is that the samba file system creates 2 events for a new or changed file while saving a file. The first event is caught by the filewatcher but at that time the file is still empty, then there is that second event and the file gets parsed normally. From a java perspective there is no chance of distinguishing those two events, so we have to live with that warning while working on a remote filesystem like samba which creates such 2 events.
