fixed bug in edit which sometimes would not remove the old value
attempted fix for #22 to try avoid jetty locking the files which breaks "mvn -Pwatch" on windows
added building notes around #203 and also added details on how to run the unit tests
fix typo
fix occasional exception
added missing jquery-datatable constant - and renamed file to correct typescript naming conventions
isolate the fix for #22 for the jetty file lock - limit the change to windows only
initial support for lazy loading of tree nodes for cases where a node has lazy loaded children for #220. Works OK but currently it would be nice to know up front which nodes have a lazy load handler registered; so we can set the lazy loading flag accordingly; to make sure things which will never be a folder appear as a leaf
add phantomjs via npm install so we can start to use it for unit tests / integration tests more easily
Allow Jasmine unit tests to be run from the Maven build

It uses PhantomJS to execute SpecRunner.html and collects the results in target/surefire-reports. SpecRunner.html can also still be run directly from the browser as before.
Right now it's still a in a separate profile called 'jasmine-test'.
The integration uses jasmine.phantomjs-reporter.js, core.js and phantomjs_jasminexml_runner.js from the https://github.com/detro/phantomjs-jasminexml-example project. The author has given kind permission to use his code for other projects: https://github.com/detro/phantomjs-jasminexml-example/issues/2#issuecomment-10619232
Enable the running of Jasmine unit tests by default.
fixes #220 so that we can enable lazy loading on specific kinds of folders using a list of factories (which by default is registered on a per domain basis). There's a slight hack using the loader callback to ensure we initialise the jmx lazy loading registry before we start loading the jmx tree ;) but at least now we only enable lazy loading for nodes that really need it
enable livereload in the unit tests
added documentation on how to use LiveReload with the unit tests
improved docs for running unit tests via maven, or via the HTML or via LiveReload
Implement the checkbox control
Display Exported Package attributes and directived as popover, for #196

The exported packages in the single bundle view now have a popover that combines information from the manifest header with the information obtained from Package Admin.
The 'Version' is the actual version, as reported by Package Admin. The other directives and attributes are obtained from the Bundle Manifest are merged with this info, and nicely formatted.
added a little bit of diagnostic logging just in case the lazy loading goes a bit wonky
added nicer tree for the route camel nodes
Add prefixfree to handle browser specific css prefixes