commit 9de3ce07e6b287c48c2c2d52a84534ed48932579
author Rob Daugherty <rd472p@att.com> Fri Aug 04 12:15:51 2017 -0400
committer Rob Daugherty <rd472p@att.com> Fri Aug 04 12:15:51 2017 -0400
tree 527206b2c6eaf2d687a84adc50405e8d690c7c7c
parent 56e4cb317b83090d1caf92ae2536d1173f507192

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.<project>
	   --or--
	org.onap.<project>

The top-level artifact is no exception.  So for example, this is
NOT allowed:

	<groupId>org.openecomp</groupId>
	<artifactId>so</groupId>

Here's what I'm trying now.  The top level pom will contain:

        <groupId>org.openecomp.so</groupId>
        <artifactId>so-parent</artifactId>

Child modules will contain:

        <parent>
                <groupId>org.openecomp.so</groupId>
                <artifactId>so-parent</artifactId>
                <version>1.1.0-SNAPSHOT</version>
        </parent>

        <groupId>org.openecomp.so</groupId>
        <artifactId>some-child-artifact</artifactId>

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 <rd472p@att.com>

packages/docker/pom.xml

diff --git a/packages/docker/pom.xml b/packages/docker/pom.xml
index 5eba3f0..c37d68a 100644
--- a/packages/docker/pom.xml
+++ b/packages/docker/pom.xml
@@ -3,13 +3,13 @@
 	<modelVersion>4.0.0</modelVersion>
 
 	<parent>
-		<groupId>org.openecomp.so.framework</groupId>
+		<groupId>org.openecomp.so</groupId>
 		<artifactId>packages</artifactId>
 		<version>1.1.0-SNAPSHOT</version>
 	</parent>
 
 	<packaging>pom</packaging>
-	<groupId>org.openecomp.so.framework</groupId>
+	<groupId>org.openecomp.so</groupId>
 	<artifactId>docker</artifactId>
 
 	<name>MSO Docker Deliveries</name>