[
https://issues.apache.org/jira/browse/HADOOP-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078934#comment-13078934
]
Luke Lu commented on HADOOP-7506:
---------------------------------
The patch itself won't work for cross-module projects. Especially if downstream
projects use ivy. We have to do some controlled version variable expansion like
what I did for MR-279.
However the maven-release-plugin way doesn't really work either, especially for
CI, as I argued in [MNG-624|http://jira.codehaus.org/browse/MNG-624] and
[MNG-2971|http://jira.codehaus.org/browse/MNG-2971]. Creating new tag/branch
for each CI build (requires a different version instead of just
something-SNAPSHOT) is extremely slow and unwieldy.
> hadoopcommon build version cant be set from the maven commandline
> -----------------------------------------------------------------
>
> Key: HADOOP-7506
> URL: https://issues.apache.org/jira/browse/HADOOP-7506
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.23.0
> Reporter: Giridharan Kesavan
> Assignee: Giridharan Kesavan
> Attachments: HADOOP-7506.PATCH
>
>
> pom.xml had to introduce hadoop.version property with the default value set
> to the snapshot version. If someone during build time want to override the
> version from maven command line they can do so by passing
> -Dhadoop.version="". For ppl who doesnt want to change the default version
> can continue building.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
