+ Max + Jimmy SO cannot use 1.2.1-SNAPSHOT because it is a snapshot, and another rule prevents release builds from depending on snapshot artifacts.
These versions of aai-common:aai-schema are in nexus: 1.2.1-SNAPSHOT - Mar 26 - depends on oparent:1.0.0 (exists) 1.2.0 - Mar 12 - depends on oparent:1.1.0-SNAPSHOT (missing) 1.1.1 - Dec 11 - depends on oparent:1.0.0-SNAPSHOT (exists) 1.1.0 - Nov 9 - depends on oparent:1.0.0-SNAPSHOT (exists) It appears that LF removed the oparent:1.1.0-SNAPSHOT artifact late on Friday. From: Williams, Marcus [mailto:[email protected]] Sent: Monday, March 26, 2018 4:27 PM To: onap-discuss <[email protected]> Cc: 'Seshu m' <[email protected]>; DAUGHERTY, ROBERT E <[email protected]> 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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_snapshots_org_onap_oparent_oparent_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=1avnrliG2ZNIjGQV4rWQZg&m=RWZ1vQlZen1Sqq-E9Au3X1WzEqm63sm9sbASIlDJV50&s=-IX7HoO7UBBCjq0hUarDY8r6uJodmwdl0-UvKxdnNHc&e=> ): 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_releases_org_onap_aai_aai-2Dcommon_aai-2Dcommon_1.2.0_aai-2Dcommon-2D1.2.0.pom&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=1avnrliG2ZNIjGQV4rWQZg&m=RWZ1vQlZen1Sqq-E9Au3X1WzEqm63sm9sbASIlDJV50&s=_Eeb2wOtDXY04u05_3dn_-Gn7rez98OXt9UZJjb2_6g&e=> 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
