fixing some compiler warnings in inline tag handler
using a mock watch service for most file modification service tests
removing 'FileModificationWatcherThread.start() in a test that was accidentally added
updating all file versions if we get an OVERFLOW event from the java watch service
making sure we cancel and remove references to any invalid watch keys
logging a warning if a watch key could not be reset but the path still exists
Merge branch 'develop' into file-change-watcher-refinements
fixing how/when the watch key reset warning is logged
test path is displayed when running tests from command line
updating Gradle to 2.2
changing gradle test logging to debug CI failures in GO
temporarily ignoring some FileModificationWatcherThreadTests incase they are causing the CI failures
Revert "temporarily ignoring some FileModificationWatcherThreadTests incase they are causing the CI failures"

This reverts commit 2e148ce272813a2bc6192219c2992ad0d5dbea23.
Revert "changing gradle test logging to debug CI failures in GO"

This reverts commit 35e82c6847ce7db90de76053bc118efe4872c329.
unified getTestPath method
Merge branch 'master' into file-change-watcher-refinements
Merge branch 'mocks-for-file-modification-thread-test' into file-change-watcher-refinements

Conflicts:
	brjs-core/src/main/java/org/bladerunnerjs/memoization/FileModificationWatcherThread.java
	brjs-core/src/main/java/org/bladerunnerjs/plugin/plugins/bundlers/inline/InlineTagHandlerPlugin.java
changing 'watch key could not be reset' log level to debug
incrementing all file versions if there is an OVERFLOW event on the watch service
increasing the watch service sensitivity if the neccessary class is available