hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15369) Avoid usage of ${project.version} in parent poms
Date Mon, 16 Apr 2018 16:13:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439645#comment-16439645

Xiaoyu Yao commented on HADOOP-15369:

I agree with [~bharatviswa] that we need to document this. [~elek] , can you add the additional
step to release after this patch in the hadoop wiki if this has not been added yet? 

> Avoid usage of ${project.version} in parent poms
> ------------------------------------------------
>                 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
>            Priority: Major
>         Attachments: HADOOP-15369-trnk.001.patch
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message