* MNT-23878: By default there was no timeout set for HttpClients, we've wrongly directed ourselfes with the values of currently existing mTLS (Solr/Elasticsearch) for Transform that used default http clients with infinite timeouts
* Set property values to the ones being set for sharedFileStoreConnector, since the only difference is the number of connections, which doesn't work in community-repo due to how the http clients are created per request of transform
* Missing property doesn't allow for providing value from JAVA_OPTS of docker image
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* Revert "ACS-3402 Camel upgrade"
This reverts commit 124e188027.
* Moving all netty dependencies up to community-repo
These dependencies are a re/declaration of transitive/optional camel dependencies used in dependant projects.
They must be in sync with camel version of community repo, hence declaring them in other projects just causes unnecessary confusion.
* Fixing new versions of netty
They were updated through transitive update of camel from .73.Final to .79.Final, along with netty-transport-native-unix-common library that went to .79.Final
* Had extreme collisions on netty-transport-native-unix-common
Moved to approach with just declaring additional non-provided netty libraries and moving version numbers to community-repo.
Even mentioning netty-transport-native-unix-common in pom.xml seems to crash tests no matter which version is taken or if it's a transitive dependency of netty-handler. Since I can't add it either way, then partial additions of libraries make no sense. I've adjusted comments next to version numbers to make it easier to differentiate what they are responsible for and need to keep track of. Version numbers should still be placed in community-repo
* 3.18.2 was released recently, doesn't modify netty versions, so I'll use the latest one
Co-authored-by: pzurek <Piotr.Zurek@hyland.com>
Implementing access restriction for actions
Updating copyrights of modified files
Moving core restriction processing to an AbstractBase class
PR Review fixes
Slight improvement for future extensibility
Not much happens in class, check node, create version.
Added Beans including security interceptors, but VersionService has no restrictions and for node service all there is are a few checks, so it likely never was a security issue to begin with.
* ACS-2850: fix for intermittent failure on expiryLock test
First issue was int rounding of '(expirationDate - new Date())/1000', which for really close values of timeout set and passed through lockInfo could be rounded down to 0. Replaced by a rounding up formula.
Second issue was treating timeout == 0 as timeout.infinite. WebDav Infinite timeout has it's own marker "-1", in case of 0, lock was automatically turned into infinite time lock, while it should be an exception instead as creating a lock for 0s timeout is a programming error - the lock would immediatelly be expired upon creation (perhaps even with a date in the past, seeing as the expiryDate is filled).
Changes made clarify the intent behind calling the method instead of obfuscating it by passing the int value through date operations
* ACS-2787: Splitting AGS 01 job to 2 parts (01, 04)
For MySQL the job executes for 31-35 minutes, split this job into 2 parts to reduce max execution time for community-repo
* ACS-2787: Intermittent test failure commented out, issue created ACS-2850
* ACS-2787: Commenting out intermittent failure, issue created ACS-2851
Marcin Strankowski
