Do you want a Jira entry for the patch?
That would be good!
I've called the splitted class FilesystemAlterationObserver (the one containing the observation code, and yes, any better naming suggestion welcome) and left the the FilesystemAlterationMonitor just with the Runnable logic.
Hm.. no better idea yet
All test run through as before (there was one which failed, and still failes after refactoring, so I guess it still does what was expected :-).
somehow ;)
Is there any reason to use commons-collection 3.1 over 3.2? 3.1 has deprecated MultiHashMap, so I've upgraded to 3.2 and replaced it with the suggested MultiValueMap.
Sounds all good! cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
