Elek, Marton created HADOOP-15369:
-------------------------------------
Summary: Avoid usage of ${project.version} in parent pom
Key: HADOOP-15369
URL: https://issues.apache.org/jira/browse/HADOOP-15369
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 3.2.0
Reporter: Elek, Marton
Assignee: Elek, Marton
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|https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance]:
{quote}
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.
{quote}
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
