[
https://issues.apache.org/jira/browse/HADOOP-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078968#comment-13078968
]
Alejandro Abdelnur commented on HADOOP-7506:
--------------------------------------------
@Luke, I was not suggesting to use the maven-release-plugin for CI. I didn't
know CI was the main motivation of the patch. Still for CI.
The release plugin is quite handy when it comes to do a release of a
multi-module project, taking care of tagging, updating to the release version
all artifacts, deploying them, and updating the version to the new devel
version.
Not yet, but eventually we should use. Because of this, versions should not be
parameterized, else the release plugin will not do its magic there.
Maybe the versions plugin could be use for this purposes during the CI:
http://mojo.codehaus.org/versions-maven-plugin/index.html
> 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: Sub-task
> 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
