CDS UI POM XML update required: use  org.onap.ccsdk.cds.controllerblueprints:blueprint-proto maven artifact instead of org.onap.ccsdk.cds.components:proto-definition

 

 

 

Yes Dan, In order to avoid cyclic dependencies we moved and renamed the module, This has been communicated earlier.

 

Yuri,

Please track this issue with UI team, and ask them to use  org.onap.ccsdk.cds.controllerblueprints:blueprint-proto maven artifact instead of org.onap.ccsdk.cds.components:proto-definition

 

 

Regards,.
Brinda Santh, Muthuramalingam
IBM - AT&T Account;
MD2-3F-003 | +91 80-402-56603 | +91 9686011661
brindasanth@in.ibm.com
Manager Name : Deepak ED | edeepak@in.ibm.com | 91-988-051-0678

-----"TIMONEY, DAN" <dt5972@att.com> wrote: -----

To: "brindasanth@in.ibm.com" <brindasanth@in.ibm.com>, "MALAKOV, YURIY" <ym9479@att.com>
From: "TIMONEY, DAN" <dt5972@att.com>
Date: 11/14/2019 04:53PM
Subject: [EXTERNAL] CDS docker build failing

Brinda, Yuriy:

 

I released the ccsdk/parent poms and tried doing a staging (and docker) build for CDS, but found the build is still failing.

 

The error that I saw in the Jenkins job was simple enough – the <relativePath> in ms/blueprintsprocessor/application/pom.xml is wrong:

 

-        <relativePath>..</relativePath>

+        <relativePath>../parent</relativePath>

 

I made that change in my local env and tried the build again, and hit a different error:

 

[*ERROR*] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack*(unpack-blueprint-grpc-proto)* on project ui-server: Unable to find/resolve artifact.: Failure to find org.onap.ccsdk.cds.components:proto-definition:jar:0.7.0 in https://nexus.opendaylight.org/content/repositories/public/ was cached in the local repository, resolution will not be reattempted until the update interval of opendaylight-mirror has elapsed or updates are forced -> [Help 1]

[*ERROR*] 

 

I tried reversing the order of the modules in cds/pom.xml to build ms before cds-ui, but that didn’t help.   It looks like that artifact no longer exists (I did a find to look in all the pom.xml’s in cds and didn’t see that artifact being built).

 

Did that artifactId change to blueprint-proto by any chance?

 

This is blocking us from doing docker builds, so I’d appreciate if you could take a look.

 

Thanks!

Dan

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@att.com

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873