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

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.2.0
    • Fix Version/s: 3.2.0
    • Component/s: build
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      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

          Issue Links

            Activity

              People

              • Assignee:
                elek Elek, Marton
                Reporter:
                elek Elek, Marton
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: