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
minor refactor following code review + adding new test for when comparison value is 0
Finessed the v0.14 release notes so they are less technical, and concentrate on the high-level features people will actually be affected by.
Moved most recently added section to correct part of the release notes.
changing comment style as it was causing a Global entry in the jsdoc (+ correcting English)
Updated release notes with the latest information we have about the file-watch problems, and our plan to create a patch release that fixes these issues.
Merge pull request #1073 from BladeRunnerJS/develop

v0.14 release
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
making watch service an interface so we can have 2 implementations
creating a WatchService factory
adding the extra WatchServices that are used if the relevant classes are available