* use jakarta-migrated community-repo
* use jakarta-migrated community-repo and community-share
* build jakarta dependencies for community-repo
* temporarily do not build share
* fix parent pom version
* use -force option to fix docker image build failures
* trigger build
* use correct versions of community-share and acs-packaging
* update community-repo version
* Use released share zip
* Bump cargo-maven3-plugin tomcat version from 9x to 10x
* revert to Tomcat9x
* bump community-repo from 161-SNAPSHOT to 163-SNAPSHOT
* Bump cargo-maven3-plugin tomcat version from 9x to 10x
* Minor changes to tomcat deployment test
* Bump community-repo from 163-SNAPSHOT to 164-SNAPSHOT
* Include Tomcat deployment test as condition for docker images update
* Changes to community_test_tomcat_deployment
* Correct community-repo version
* Bump community-repo version to 23.1.0.170-SNAPSHOT
* Pin acs-packaging version to A27 for share compatibility
* Workaround for not migrated share
* Disable Tomcat deployment test
* Update latest docker images no longer relies on tomcat deployment test
* As per [ACS-5545] -force flag should not be needed
* Remove jakarta-dependencies build from script
---------
Co-authored-by: pzurek <Piotr.Zurek@hyland.com>
Co-authored-by: Kacper Magdziarz <95610011+kmagdziarz@users.noreply.github.com>
Co-authored-by: kmagdziarz <Kacper.Magdziarz@hyland.com>
Sara
