Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15369

Avoid usage of ${project.version} in parent poms

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.2.0
    • 3.2.0
    • build
    • None
    • Reviewed

    Description

      hadoop-project/pom.xml and hadoop-project-dist/pom.xml use ${project.version} variable in dependencyManagement and plugin dependencies.

      Unfortunatelly it could not work if we use different version in a child project as ${project.version} variable is resolved after the inheritance.

      From maven doc:

      For example, to access the project.version variable, you would reference it like so:

      <version>${project.version}</version>

      One factor to note is that these variables are processed after inheritance as outlined above. This means that if a parent project uses a variable, then its definition in the child, not the parent, will be the one eventually used.

      The community voted to keep ozone in-tree but use a different release cycle. To achieve this we need different version for selected subproject therefor we can't use ${project.version} any more.

      Attachments

        1. HADOOP-15369-trnk.001.patch
          23 kB
          Marton Elek

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            elek Marton Elek
            elek Marton Elek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment