* master: (52 commits)
[maven-release-plugin][skip ci] prepare for next development iteration
[maven-release-plugin][skip ci] prepare release 2.5.7-A4
ACS-2587 Fix test failure
ACS-2587 Include directAccessUrl in T-Config if supported (#539)
ATS-864: fix dependabot
ATS-864: Switch from fabric8 to docker mvn plugin (#436)
ACS-2072 Enforce third party license compliance.
[maven-release-plugin][skip ci] prepare for next development iteration
[maven-release-plugin][skip ci] prepare release 2.5.7-A3
[trigger release] 2.5.7-A3
Bump activemq-client from 5.16.3 to 5.16.4 (#534)
Bump maven-javadoc-plugin from 3.3.1 to 3.3.2 (#533)
ATS-981 Avoid CVE-2022-23181 with spring-boot-starter-web 2.6.3 (#537)
[maven-release-plugin][skip ci] prepare for next development iteration
[maven-release-plugin][skip ci] prepare release 2.5.7-A2
[trigger release] 2.5.7-A2
ACS-2497 Rework httpTransformRequestUsingDirectAccessUrlTest so it can be used in AI and Aspose (#535)
Bump docker-maven-plugin from 0.38.1 to 0.39.0 (#528)
[maven-release-plugin][skip ci] prepare for next development iteration
[maven-release-plugin][skip ci] prepare release 2.5.7-A1
...
# Conflicts:
# .travis.yml
# alfresco-transformer-base/src/main/java/org/alfresco/transformer/util/RequestParamMap.java
Also bumped pom.xml version (for two ffmpeg folders) from 2.5.5-A2-SNAPSHOT to match others (2.5.7-A5-SNAPSHOT)
The t-config returned by the T-Router & T-Engines should include directAccessUrl as an optional transform option when the T-engine supports it.
[trigger release] 2.5.7-A4
* ACS-2497 Add implementation of Direct Access Url usage for transformation.
Add possibly to pass Direct Access Url to Transform request instead of a sending a file.
The bulk of the changes in this PR are to do with adding a coreVersion element to the transform element in the T-Engine config. For more detail see the class header of CoreVersionDecorator.
* Support the use of coreVersion so that it is possible to upgrade pods in any order
* Moved the majority of the RequestParamMap static finals to alfresco-transform-model and added a new one: "includeCoreVersion" parameter.
- went from green to red (when building docker image - apparently change in FFmpeg install)
- took the opportunity to switch to supported Java Base Image (ie. CentOS 7 LTS instead of CentOS 8)
- hence, for now (for PoC) floating FFmpeg v3.x (rather than v4.x)
* ACS-2499 Delete company release build stage.
This never uploaded any software, and so was not particularly useful. The software and license report should be
uploaded to S3 as part of the transform-service build.
Also skip uploading anything to staging bucket.
* Repeat Bump dependency.tika.version from 2.1.0 to 2.2.1
Original PR https://github.com/Alfresco/alfresco-transform-core/pull/506 was merged to master where it failed. There had been no build of the PR before the merge, which is why this branch has been created.
* Use non deprecated TikaCoreProperties.SUBJECT with tika 2.2.1.
The deprecated OfficeOpenXMLCore.SUBJECT value worked in 2.2.0 but not 2.2.1
* With the upgrade of Tika from 2.2.0 to 2.2.1, the deprecated OfficeOpenXMLCore.SUBJECT metadata value became being null and the replacement TikaCoreProperties.SUBJECT became a multi value in a few of our test cases. For backward compatibility with very old versions of Alfresco, we have historically been added a number of extra values including "subject" and "description" back into the raw metadata, before mapping them onto Alfresco properties. These values existed in the original version of Tika used by Alfresco, so it is possible there are custom mappings out there that using them.
To complicate matters a little, out standard mappings for some types put the raw "subject" value into cm:description property. What makes it interesting is that the extra "description" value is not used but has the value originally in our expected metadata extarct data. That is why the quick_*_json files have been modified.
