HI Marcus,

Jimmy is already working towards resolving this issue.
Thanks for the mail.

Best Regards,
Seshu
******************************************************************************************
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*****************************************************************************************
________________________________
From: Williams, Marcus [[email protected]]
Sent: Tuesday, March 27, 2018 4:26 AM
To: onap-discuss
Cc: Seshu m; DAUGHERTY, ROBERT E
Subject: [aai] [so] aai-common 1.2.0 depends on expired oparent snapshot

Hello AAI Team,

SO has a dependency on your aai-schema 1.2.0 release artifact, but recently all 
of our builds are failing due to this dependency.

It appears aai-common and by extension aai-schema release artifacts have a 
dependency on oparent 1.1.0-SNAPSHOT which no longer exists 
(https://nexus.onap.org/content/repositories/snapshots/org/onap/oparent/oparent/
 ):

Build failed to find artifact org.onap.oparent:oparent:pom:1.1.0-SNAPSHOT 
needed for sub-project org.onap.so:common:jar:1.2.0-SNAPSHOT: Failed to collect 
dependencies at org.onap.aai.aai-common:aai-schema:jar:1.2.0: Failed to read 
artifact descriptor for org.onap.aai.aai-common:aai-schema:jar:1.2.0. Check 
correct groupId, artifactId and version. This may also indicate a problem with 
nexus. Another possibility is that this is a -SNAPSHOT version and it has 
expired from nexus -- in that case check with the project which provides the 
artifact.

See: 
https://nexus.onap.org/content/repositories/releases/org/onap/aai/aai-common/aai-common/1.2.0/aai-common-1.2.0.pom

All of our verify builds are failing due to this dependency. It seems the 
dependency should be on oparent 1.1.0 and not 1.1.0-SNAPSHOT.

I think we can work around temporarily by using aai-schema 1.2.1-SNAPSHOT which 
is based on oparent 1.1.0. However it would seem reasonable to fix this 
dependency issue on AAI released artifacts side.

Cheers,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. – Network Platforms Group

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to