SDK trying to deploy an artifact when the artifact is already exist in repository.
One premium jmix-addon installed successfully, but next one is failed.
Tested with archive jmix-dependencies-1.3.5.zip
and cuba-sdk-1.2.8
Set Deployment policy = Disable redeploy for your repository.
Import zip-archive, set your license key and install one of premium jmix-addons (e.g. Maps as in the instruction).
(One premium addon installed successfully.)
Then try to install another premium jmix-addon (BPM, WebDAV or Notifications).
ER: All premium addons installed successfully.
AR: FAILURE: Command execution failed with an exception.
What went wrong:
Unable to upload MvnArtifact(groupId=ch.qos.logback, artifactId=logback-classic, version=1.2.11, classifiers=[Classifier(type=, extension=jar), Classifier(type=, extension=pom), Classifier(type=sources, extension=jar)]). Error: Could not execute build using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-6.6.1-bin.zip'.
Second jmix addon is resolved, but not installed. (You can use a command list jmix-addonto check it).
NB: If I change the Deployment policy to Allow redeploy, all premium addons installed successfully.
I believe that SDK should check if there artifact in repository
and shouldn't try to deploy it when the artifact is already exist in the repo.
SDK trying to deploy an artifact when the artifact is already exist in repository. One premium jmix-addon installed successfully, but next one is failed.
Tested with archive jmix-dependencies-1.3.5.zip and cuba-sdk-1.2.8
Steps to reproduce:
ER: All premium addons installed successfully.
AR: FAILURE: Command execution failed with an exception.
Second jmix addon is resolved, but not installed. (You can use a command
list jmix-addonto check it).NB: If I change the Deployment policy to Allow redeploy, all premium addons installed successfully.
I believe that SDK should check if there artifact in repository and shouldn't try to deploy it when the artifact is already exist in the repo.