...

Ultimately this will ensure consistency across ONAP projects, and free individual projects from redundant work whenever the standard configurations need to be changed.

Release Notes

...

Frankfurt

https://docs.onap.readthedocs.ioorg/enprojects/latestonap-integration/submodules/integration.git/docsen/frankfurt/release-notes.html#ohtml#release-parent.notes

How to Implement for Your Project

...

    <!-- NOT RELEASED YET - TARGET IS M1 -->


	<parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>3.12.0-SNAPSHOT<0</version>
        <relativePath/>
    </parent>

Formatting Plugin Now Available Starting in guilin- 25 Jun 2020 

Oparent now has a formatting plugin available for projects that need to get their source code formatted to meet checkstyle guidelines. Instructions are in the pom.xml on how to use it.

...

# Clone oparent somewhere local
> git clone https://github.com/onap/oparent.git 

# 1st - your project should be inheriting from this oparent java dependency
> cd <my-repo>
> vi pom.xml

# ensure pom.xml is pointing to 3.1.0-SNAPSHOT or later

# 2nd - go into your project's source directory you wish to reformat
> cd <my-repo-to-reformat>

# 3rd - type in the following and make sure you set the path to where you have oparent cloned and its
              onap-java-formatter.xml file

> mvn formatter:format spotless:apply process-sources -Dproject.parent.basedir=<oparent-clone-location>

# formatter will re-format your source files

# check that the source compiles
> mvn clean install

# the source changes can now be uploaded via git review process

CVE Profile Now Available starting in guilin- 26 Jun 2020 

This profile can be used offline to check a repository for CVE issues in the codebase. Useful for contributors to check a new dependency without waiting for code to be merged and a CLM report job to be run.

...

Previous Versions of Oparent

    <!-- LATEST RELEASE RELEASED VERSION WILL BE AVAILABLE 1st HALF 2022 -->

    <!-- AVAILABLE SNAPSHOT -->

    <parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>3.3.0.2<-SNAPSHOT</version>
        <relativePath/>
    </parent>

    <!-- CurrentRELEASED SNAPSHOTVERSION -->

	<parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>3.2.1</version>
        <relativePath/>
    </parent>

   <!-- AVAILABLE SNAPSHOT -->

	<parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>3.02.32-SNAPSHOT</version>
        <relativePath/>
    </parent>

    <!-- LATESTRELEASED RELEASEVERSION -->

	<parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>3.1.0</version>
        <relativePath/>
    </parent>

    <!-- RELEASED VERSION -->

	<parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>2<version>3.1.0</version>
        <relativePath/>
    </parent>

    <!-- CurrentLAST AVAILABLE SNAPSHOTRELEASE -->
    <parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>2<version>3.20.0-SNAPSHOT<2</version>
        <relativePath/>
    </parent>

    <!-- LAST AVAILABLE RELEASE -->
    <parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
        <version>2.1.0</version>
        <relativePath/>
    </parent>

Remove redundant configuration items

...

1. Update the dependencies/pom.xml and dependencies-clm/pom.xml with any updated versions of upstream projects.
   1. this should be done with the security team to identify the acceptable or better version
   2. project team repos should also be validated to make sure they understand any implications on client code before they up-rev
   3. The merge of this change should create a maven merge job log that can be referenced
   4. This should be X.Y.Z-SNAPSHOT as the revision.
2. Discuss at the PTL call that an updated version of OPARENT will be released.
3. Use the LF self-release process to create the releases/X.Y.Z.yaml file that points to the maven merge job and the release number
   1. https://gerrit.onap.org/r/#/c/oparent/+/94862/
4. The self release jobs should run and publish the maven artifact for X.Y.Z release.
5. After that job runs you need to up-rev the Patch version of oparent
   1. https://gerrit.onap.org/r/#/c/oparent/+/94863/
   2. This changes the revision to X.Y.Z+1-SNAPSHOT (or whatever X,Y,Z combination is appropriate) in all the affected files.
6. oparent repository would now be ready for step 1.

...