Remove self references in oparent 07/132707/4
authorliamfallon <liam.fallon@est.tech>
Wed, 14 Dec 2022 09:59:46 +0000 (09:59 +0000)
committerliamfallon <liam.fallon@est.tech>
Wed, 14 Dec 2022 11:50:16 +0000 (11:50 +0000)
commit5688c492c5e6760a99e1fb9853b891661665bb36
treea10dcd83628cc94435440365516b5849973d9476
parent1777b660036ec994ef5874d3eb567def38541f96
Remove self references in oparent

This commit removes self references in oparent. These self references
mean that the version of an import in oparent is set to the value of
project.version, which is the value of project.version in the project
importing oparent, not the actual version of oparent. This causes all
sorts of side effects.

The down side is that users of oparent will now have to explicitly
import the oparent dependencies, doing somethling like:

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.onap.oparent</groupId>
        <artifactId>dependencies</artifactId>
        <version><Your oparent version></version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

Issue-ID: POLICY-4482
Change-Id: I573bffb0656209413fafc3800c3bcbdb616beecd
Signed-off-by: liamfallon <liam.fallon@est.tech>
dependencies-clm/pom.xml
oparent/pom.xml