Uploaded image for project: 'Common Controller SDK'
  1. Common Controller SDK
  2. CCSDK-1300

Use of artifact version in POM files

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Dublin Release
    • Dublin Release
    • sli/core
    • None

      When doing a build, consistent versions for artifacts to be used for dependency management, when parent POM's are expected to drive consistent versioning. Please review  few such following instances and not sure why <project.version> is used instead of <ccsdk.sli.core.version>:

      https://gerrit.onap.org/r/gitweb?p=ccsdk/sli/core.git;a=blob;f=sli/features/odl-sli/pom.xml;h=219ee7cd2b418e2aa25590a241bdc824a257b978;hb=refs/heads/dublin

      https://gerrit.onap.org/r/gitweb?p=ccsdk/sli/core.git;a=blob;f=dblib/features/ccsdk-dblib/pom.xml;h=dd26fe87ed935a9f13ad5a4c1bfac404d5fd1b71;hb=HEAD

      https://gerrit.onap.org/r/gitweb?p=ccsdk/sli/core.git;a=blob;f=dblib/features/features-dblib/pom.xml;h=5adff72f94f92bfa2afff502b8c6118c2b6cb9c2;hb=HEAD

      During CCSDK build, when I use say 0.4.2-SNAPSHOT as project version, and also use parent POM's that refer to 0.4.2 as ccsdk.sli.core.version, my builds always fail. It may be due to inconsistent version used. Please advise. Thank you!

            djtimoney Dan Timoney
            sandeeplinux sandeeplinux
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: