[ https://issues.apache.org/jira/browse/HBASE-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108363#comment-13108363 ]
Joep Rottinghuis commented on HBASE-4447: ----------------------------------------- Before patch: mvn clean install -DskipTests=true -Dhadoop.profile=22 -Dhadoop.version=0.22-argon-SNAPSHOT > build.log look in workspace/target directory: hbase-0.92.0-SNAPSHOT.tar.gz and hbase-0.92.0-SNAPSHOT.jar are produced. After patch: mvn install -DskipTests=true -Dhadoop.profile=22 -Dhadoop.version=0.22-argon-SNAPSHOT -Dhbase.version=0.92-joep-0 > build.log look in workspace/target directory: hbase-0.92-joep-0.tar.gz and hbase-0.92-joep-0.jar are produced. > Allow hbase.version to be passed in as command-line argument > ------------------------------------------------------------ > > Key: HBASE-4447 > URL: https://issues.apache.org/jira/browse/HBASE-4447 > Project: HBase > Issue Type: Improvement > Components: build > Affects Versions: 0.92.0 > Reporter: Joep Rottinghuis > Attachments: HBASE-4447-0.92.patch > > > Currently the build always produces the jars and tarball according to the > version baked into the POM. > When we modify this to allow the version to be passed in as a command-line > argument, it can still default to the same behavior, yet give the flexibility > for an internal build to tag on own version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira