-
Bug
-
Resolution: Done
-
High
-
Honolulu Release
Since 21/06/01 ccsdk/feature/sdnr artifacts are build correctly, but deployment to nexus does not work.
Suspect that problem caused by "deployeAtEnd true" in maven-deploy-plugin config by https://jira.onap.org/browse/CCSDK-3126
Indication is this artifact, with last update on Fri Feb 05 2021 20:05:01 GMT+0100 (Central European Standard Time)
<dependency> <groupId>org.onap.ccsdk.features.sdnr.wt</groupId> <artifactId>sdnr-wt-feature-aggregator-installer</artifactId> <version>1.1.1-SNAPSHOT</version> <type>pom</type> </dependency
(https://nexus.onap.org/#nexus-search;quick~sdnr-wt-feature-aggregator-installer)
Referring to Successful build with the problem:
Artifacts that are NOT pushed, have the deployment output like this (They are not listed on the uploaded list at the very end of build console output and seem no to be in the repository "/w/workspace/ccsdk-features-maven-merge-master/m2repo"):
18:59:59 [INFO] --- maven-deploy-plugin:2.8:deploy (default-deploy) @ sdnr-wt-feature-aggregator-installer --- 18:59:59 [INFO] Deploying org.onap.ccsdk.features.sdnr.wt:sdnr-wt-feature-aggregator-installer:1.1.1-SNAPSHOT at end
Artifacts that are pushed are writing this:
18:42:43 [INFO] --- maven-deploy-plugin:2.8:deploy (default-deploy) @ ccsdk-features-all --- 18:42:43 [INFO] Using alternate deployment repository staging::default::file:/w/workspace/ccsdk-features-maven-merge-master/m2repo 18:42:43 [INFO] No primary artifact to deploy, deploying attached artifacts instead.
Last correct build is this:
- relates to
-
CCSDK-3126 CCSDK parent : Adding deployAtEnd true to maven-deploy-plugin
- Closed