Now the JCR repository initialization takes into account of the org/silverpeas/util/jcr.properties file to set the repository home directory
Bug #5197 - fixing displaying of old wysiwyg attachments after a 5.12 migration on a Silverpeas with multilingual content activated...
- fixing also the display of wrong content according to the selected content language
Bug #5197 - fixing a technical error on windows platform around the computing of the JCR home directory path
Bug #5197 - improving the wysiwyg adjustment treatment to take in account additional cases of problems
Bug #5197 : modifying the name of the called method for document adjustment in order to prevent call of treatments that were already existing but with wrong corrections (Fortunately, these wrong corrections were never called by dbBuilder).
Bug #5197 - taking into account old documents from which update date could be null ...
Feature #4843 : blocking the download of file attachments attached to publications
- upgrading the definition of the Silverpeas JCR data structure (adding a new information)
bug #5308 :   Unescape all HTML entites in the publications and in the comments updated since 2013-10-07 (the release of 5.12.4)
fixing into the migration wysiwyg adjustment a potential wysiwyg loss due to an unexpected wysiwyg management behavior (the copy of a publication for example)
set parent POM version to 27
[maven-release-plugin] prepare release configuration-5.14
[maven-release-plugin] prepare for next development iteration
set the version of the Parent POM to 28-SNAPSHOT
Bug #5329 - adding a treatment to purge empty WYSIWYG contents
(adding JCR unit tests ...)
(adding a treatment in order to rename physical WYSIWYG file name according to the language)
Bug #5780 - removing dbBuilder crashes on inconsistent JCR data detection.
Now, when an expected file is not found, the purge process continues and an error is logged.
Bug #5780 - adding some date/time and duration log information.
Bug #5780 :
- improving significantly the performance
- adding some other date/time and duration log information.
Bug #5780 :
- refactoring the code to handle as a centralized way a thread pool executor for which the number of threads is settable
Refactor the test so the spring context bootstrap and the database settings are done each of them within a distinct JUnit Rule