REPO-361 use patched jr that includes fix for workspace move

REPO-361 use patched jr that includes fix for workspace move

REPO-360 workspace move can be fixed easily after all

REPO-360 workspace move can be fixed easily after all

REPO-360 log warning when workspace.move is used

REPO-360 log warning when workspace.move is used

REPO-361 use newly patched jr with inconsistency fixes

REPO-361 use newly patched jr with inconsistency fixes

REPO-354 support validate hierarchy option

REPO-360 use session move instead of workspace move to prevent data corruption with concurrent writes

REPO-360: use session save instead of node save

REPO-358:prepare for next development iteration

REPO-358:prepare release hippo-repository-2.20.10

REPO-359: simple guard against invalid class loading

CMS7-5744: copy defaultwrite domainrules into defaultread to grant correct read
access to everybody

backport from trunk

CMS7-5969: backport

CMS7-5969: also release the types structure when an object is placed back (to mirror same operation as in fetch object)

REPO-349 reset buzy flag also when lock could not be acquired

REPO-349 reset buzy flag also when lock could not be acquired

REPO-335 log4j is pulled in transitively

REPO-335 backport event logger improvements

REPO-331 backport event logger improvements

REPO-353:  copy for tag hippo-repository-2.22.04

CMS7-5744: grant everybody at least readonly access

At least the faceted authorization tests were assuming read access to these nodes.  This is now implemented without granting jcr write access.

REPO-352: Fix warnings reported by m2eclipse

REPO-349 use cluster node id as lock owner and use open-scoped lock instead of session-scoped lock because apparently in the former case the cluster is notified whereas in the latter it is not.

REPO-349 use cluster node id as lock owner and use open-scoped lock instead of session-scoped lock because apparently in the former case the cluster is notefied whereas in the latter it is not.

REPO-314: repository-resources web.xml contains repository-directory as an init-param - backport

REPO-349 better log message

REPO-349 aquire lock on module configuration before executing cleanup job: don't run when already locked by other cluster node

REPO-334 fix unit test for updated way of reading cluster node id

REPO-347 German Translation

REPO-334 use repository descriptor to get cluster node id

REPO-335 backport performant event log cleanup

REPO-348 don't fail on inconsistent workspace

REPO-347 German Translation

REPO-299: enable jackrabbit hierarchy change validation when running tests

The filtered item state iterator already filtered out the external nodes that were modified in other sessions.
The same now also happens in the #has and #deleted methods in the filtered changelog itself.

REPO-308 fix npe

REPO-343 reintroduce innodb support but now without breaking support for derby

AUTOEXPORT-2 remove obsolete dependency

REPO-343 also log to console

REPO-345 add support for abandoned nodes

REPO-342: specify property type for multi-valued properties

The wrong type/definition might be used otherwise.

REPO-334 adjust log level for testing

AUTOEXPORT-2 remove auto export test

REPO-334 implement hierarchical event logger.
Events are logged in a random folder structure of depth 3. Allowing for millions of events. Each cluster node has its own subtree for events to avoid collisions and to allow observation of events for only specific clusters.

CMS7-5934 don't export null workflows

AUTOEXPORT-2 remove export module

REPO-339 don't warn when trying to remove a node that does not exit

REPO-336prepare for next development iteration