hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7506) hadoopcommon build version cant be set from the maven commandline
Date Wed, 03 Aug 2011 21:47:27 GMT

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

Luke Lu commented on HADOOP-7506:
---------------------------------

bq. Maybe the versions plugin could be use for this purposes during the CI: http://mojo.codehaus.org/versions-maven-plugin/index.html

Just verified that mvn versions:set -DnewVersion=0.23.0-my-version works without the scm stuff.
So this is a viable way for CI build, though still less convenient than version properties
which can be easily controlled by profiles (e.g., via settings.xml)

> 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

        

Mime
View raw message