From 9de3ce07e6b287c48c2c2d52a84534ed48932579 Mon Sep 17 00:00:00 2001 From: Rob Daugherty Date: Fri, 4 Aug 2017 12:15:51 -0400 Subject: Failed to deploy so artifacts in nexus (again) There are Linux Foundation rules (enforced by nexus) that I still don't really understand. I'm convinced this is absolutely true: The groupId of every artifact in a project MUST begin with: org.openecomp. --or-- org.onap. The top-level artifact is no exception. So for example, this is NOT allowed: org.openecomp so Here's what I'm trying now. The top level pom will contain: org.openecomp.so so-parent Child modules will contain: org.openecomp.so so-parent 1.1.0-SNAPSHOT org.openecomp.so some-child-artifact Note that the groupId for the direct child module will be the same as the groupId for its parent. Issue: SO-21 Change-Id: I0d3cd2eb7a1883e23e3c0878ee7fa3dd4a7d55b2 Signed-off-by: Rob Daugherty --- status-control/pom.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'status-control/pom.xml') diff --git a/status-control/pom.xml b/status-control/pom.xml index 40f3bad5f5..d1f2fb1920 100644 --- a/status-control/pom.xml +++ b/status-control/pom.xml @@ -5,11 +5,11 @@ 4.0.0 org.openecomp.so - framework + so-parent 1.1.0-SNAPSHOT - org.openecomp.so.framework + org.openecomp.so status-control MSO Status Control module Contains classes to update and query the MSO status per site @@ -22,17 +22,17 @@ test - org.openecomp.so.framework + org.openecomp.so common ${project.version} - org.openecomp.so.framework + org.openecomp.so mso-catalog-db ${project.version} - org.openecomp.so.framework + org.openecomp.so mso-requests-db ${project.version} -- cgit 1.2.3-korg