JCR-1736: Converted the doc about the Session Leak Detector into Docbook
Replacing scm urls
Upgrading maven plugins version
JCR-1736: revert commit 2a1123d621e0105ce5ce68ca9eba5c7710152c72
Fixed scm urls
JCR-1726:  Add bookId to JCR Ref Guide
JCR-1716: Doc about Access Manager is erroneous

Fix description:
	- Correct the API of some incorrect function in doc about Access Manager
JCR-1729: Remove workaround ConcurrentHashMap

Problem analysis
	- ConcurrentHashMap is caused the ConcurrentModficationException

How is the problem fixed?
	- Using iterator for removing items and replacing ConcurrentHashMap by HashMap
JCR-1725: isSuspended filed in CacheableWSDataManager, SeachManager and SearchIndex must be AtomicBoolean, index merger must be disposed after flush on close

Problem analysis
        - When calling MultiIndex.close with non empty volatile index, it invokes flush() to store changes on file system.
          But Merger already disposed and this causes exception. In addition, some flags and fields in Index and CacheableWorkspaceDataManager can be accessed within multiple threads
          but they doesn't guarantee thread safeness.

Fix description
        - Merger is disposed after calling flush() in MultiIndex.close()
          and AtomicBoolean and AtomicReference objects are used to ensure Thread-safeness in mentioned components of JCR.
JCR-1728: The JCR doc is invalid according to the DTD of Docbook 4.5 which prevents the doc of PLF to build
JCR-1742: Performance issues met with MySQL InnoDB

Problem analysis
	- PLF with MySQL InnoDB starts very slowly.

Fix description:
	- Fix contains two improvements: forced index for query and rewrote query for table checking existing.
JCR-1749 : Fix comment for AddDependenciesAfter.
JCR-1739: JCR Session unclosed in GroovyScript2RestLoader.start()

Fix description:
	* Avoid null session of GroovyScript2RestLoader
	* Log out session containing GroovyScript2RestLoader if neccessary
JCR-1747 : use secure random instead of IDGenerator in RepositoryCreationService.
JCR-1727 CS-5632: Searching in cluster sometimes returns duplication of just modified nodes

Problem analysis
	* When some JCR contents are modified, their index is deleted and re-created.
	* Content is usually stored in persistent index on file system. Modifying it causes deletion of corresponding Lucene Document on file system and reindexing into the Volatile (in memory) index
	* But actually, Lucene Document is not deleted from persistent index, it is only marked as deleted in memory buffer. This greatly improve the performance, but causes issues in clustered environment
	* Thus non-coordinator cluster nodes doesn't see the fact that node deleted and query finds it in persistent and volatile indexes causing duplication.

Fix description:
	* Issue was fixed by applying deletions on non-coordinator nodes too, but in memory only. Those deletions are cleaned once coordinator flushes its buffers.
JCR-1731: JbossCache in CacheableLockManagerImpl is not load data from cache loader after second start repository (stop and start on repository) in "jbosscache-shareable" mode.

Problem analysis
	* ControllerCacheLoader allows data loading only as startup. Since several repositories can share same JBC instance after repository restarting we can not see locks in cache lock.

Fix description
	* ControllerCacheLoader allows data loading only as startup. Since several repositories can share same JBC instance after repository restarting we can not see locks in cache lock.
Revert "JCR-1731: JbossCache in CacheableLockManagerImpl is not load data from cache loader after second start repository (stop and start on repository) in "jbosscache-shareable" mode."

This reverts commit 466db533625b2327d775938394c59b95919aadbf. Because this commit leads to test fail in exogtn
JCR-1754: Avoid pattern query when the property/node name is complete…

Problem analysis
    - The query corresponding to the method findChildPropertiesByParentIdentifierCQ is slower than one corresponding to getItemData in case of HSQLDB.

Fix description
    - Use getItemData in query instead of findChildPropertiesByParentIdentifierCQ incase of HSQLDB
JCR-1738 : Temporary file was removed if IOException occur during spooling of InputStream value

Problem analysis
	* Temporary spool file remains forever on FS after IOException

Fix description
	*  By removal or adding file to FileCleanr
JCR-1734 : The changes form stable 1.14.x branch to fix branch fix/1.14.8-GA JCR-1734.