[
https://issues.apache.org/jira/browse/HADOOP-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079144#comment-13079144
]
Scott Carey commented on HADOOP-7506:
-------------------------------------
I have given up on the maven-release-plugin. It fails in many situations, too
many of them to list here. If you want to do something like have trunk named
trunk-SNAPSHOT and branches named in custom ways, good luck. It is an example
of a design anti-pattern: it is a conflated design. It tries to do too much at
once.
Do one thing and do it well:
Use http://mojo.codehaus.org/versions-maven-plugin/ to update the version of
items in multi-module products.
Use plain old svn command line to branch/tag.
Use plain old maven to verify a build.
> 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
