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 --- packages/docker/pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'packages/docker') diff --git a/packages/docker/pom.xml b/packages/docker/pom.xml index 5eba3f0c5b..c37d68a5ed 100644 --- a/packages/docker/pom.xml +++ b/packages/docker/pom.xml @@ -3,13 +3,13 @@ 4.0.0 - org.openecomp.so.framework + org.openecomp.so packages 1.1.0-SNAPSHOT pom - org.openecomp.so.framework + org.openecomp.so docker MSO Docker Deliveries -- cgit 1.2.3-korg