Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-435

Propose and clean up pom.xml to reuse properties defined in oparent settings.xml

XMLWordPrintable

      As a part of this story, identify all the properties that are redefined in CPS. Prepare a proposal listing all the properties that need to be overriden in CPS if required.

      Few properties already defined in oparent settings.xml :

      • ${onap.nexus.dockerregistry.release} : The default onap docker registry for releasing artifacts
      • ${docker.pull.registry} : The default docker pull registry 
      • ${docker.push.registry} : The default docker push registry
      • ${onap.nexus.url} : The default onap nexus url

      CPS should reuse these properties wherever possible instead of refining them as :

      • nexusproxy : refined in CPS core - ${onap.nexus.url}  could be used instead
      • releaseNexusPath : settings.xml has the repository values already defined

       

      Out of scope

      • CPS-Temporal DB, CPS-TBDMT (will create another Jira for CPS-Temporal)

      Acceptance Criteria:

      1. Proposal created listing all the properties redefined in CPS that is already defined in oparent settings.xml
      2. Also include the list of properties that need to be overridden in CPS if any.
      3. Clean up pom.xml to remove duplicate definition of properties. (subtask)

       

       

       

            brusak brusak
            puthuparambil.aditya puthuparambil.aditya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: