Feature/outlook integration
Added a profile that can be used to automatically download and install the repo and share outlook integration AMPs.
When used with a start-* profile it allows us to run OI and RM on our development environment.
For example: mvn install -f ./rm-enterprise/rm-enterprise-repo -Pstart-repo,outlook-integration.
See merge request !394
Feature/rm 3643 patch for updating existing users and groups alternative solution
Alternative solution for the adding the new aspect to authorities that have marks (patch from 2.5-EA1 to later versions)
See merge request !345
Feature/rm 3708 ldap startup error
RM-3708 - [LDAP] Exception "NodeRef may not be null for calls to NodeService" is thrown in logs
The error is thrown when the application tries to run the disposition jobs as "$\{audit.rm.runas\}". When the value is not present in any property file the value is not interpreted.
This only reproduces when using some authentication chains because the authentication service is not reliable to check if a person exists. Some implementations of it just return true (AuthenticationServiceImpl) and some of them, in the best case scenario, reach person service to make the check.
As a fix I replaced authentication service with person service.
See merge request !378
* added root inplace group, created on start-up if not already there
* all groups created in RM zone
* fixed up file plan permission unit test and removed ignore from test
suite
* removed delimeters from groups names to keep length to a min
Change installer download logic for rm-automation
It changes from SCP to ANT get so Elastic Bamboo agents can download the installers.
This requires a change in the bamboo build plan for the {{installer.path}} variable
See merge request !362
Feature/rm 2 5 with alfresco 5 1 1
DO NOT MERGE THIS!!!
I will regularly merge master onto this branch and keep an eye on the builds. The results are looking good
See merge request !299
Feature/rm 3558 recently modified marks
@Tom can you take a look at this and let me know what you think.
The interesting changes are in the security mark content model. I've run the builds and they were green with the exception of a couple of seemingly unrelated tests (rerunning that build now to see if it makes any difference)
See merge request !341
