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
Attachments
Issue Links
- is required by
-
HDFS-13407 Ozone: Use separated version schema for Hdds/Ozone projects
-
- Resolved
-