Solve package dependency resolution during release

If a package depends on another package, then during the release process it will fail at retrieving it from Connect (since the dependency has not been deployed yet).

A workaround was to look for the more recent nuxeo-dam in the local m2 repository and add it to the server cache. But that solution does not work during the development process: packages are not deployed in Nexus and the slave performing the test may not have the dependency in its local M2 cache.

A solution for the release process could be to deploy the packages on Connect Test right after their individual build and make the functional tests run against Connect Test (it is not possible to deploy a release package in Connect at this stage).
That would be fine for the development process since it already deploys its SNAPSHOT artifacts in both Connect and Connect Test.