Merge with OO-121, OO-124 to 80-patch branch

--HG--
branch : 80-patch

INSTALL.README.HEAD

@@ -89,11 +89,6 @@ F. If you run into problems with classes or resources not found e.g. "ClassNotFo
    from eclipse to console and back with command like mvn clean, or eclipse clean and such. You will always get 
    a clean and working environment when you do the following: Eclipse clean, create eclipse settings with launch, 
    Server publish resources and restart OLAT.
-   
-G. In some eclipse setups you will get compile errors because of XML/XSLT validation errors. In this case disable all 
-   validators in the project properties (Right click on project -> "Properties" -> "Validators") and set all levels
-   for XSLT to "ignore". After this step restart eclipse and execute 'mvn eclipse:clean eclipse:eclipse' again, 
-   refresh and then clean the project to recompile.
 
 
 Background (optional for further interest)

olat.local.properties.sample

@@ -78,7 +78,10 @@ instance.id=myopenolat
 olat.debug=true
 # for developers set to false - i18n files are not cached
 localization.cache=false
-#path to the source code (for auto reload from velocity templates, )
+# path to the source code. Use this together with olat.debug=true in a 
+# development setup. If set properly, velocity templates, i18n files and 
+# static files like CSS will be reloaded from the source code on each request 
+# without redeployment of the entire webapp.
 #project.build.home.directory=/Users/srosse/workspace/OpenOLAT
 
 user.generateTestUsers=false