[
https://issues.apache.org/jira/browse/HCATALOG-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557393#comment-13557393
]
Alan Gates commented on HCATALOG-598:
-------------------------------------
The failure seems to be in test.sh, as it fails with or without Travis' new
script. It's in building the Hadoop 23 version of HCat. If the line in
test.sh that does that build is commented out then all is good.
One other comment I saw is that release.sh is not executable when applied from
the patch, but that may just be how patch works. As long as its marked
executable when it's checked in that's fine.
We also need to make sure and update the HowToRelease doc on using this.
I agree with Travis that this isn't an ideal solution but I can't think of a
better one at the moment.
So, all that said, I'm +1 on this patch.
> fix setting hcatalog version number via the command-line
> --------------------------------------------------------
>
> Key: HCATALOG-598
> URL: https://issues.apache.org/jira/browse/HCATALOG-598
> Project: HCatalog
> Issue Type: Bug
> Components: build
> Reporter: Travis Crawford
> Assignee: Travis Crawford
> Fix For: 0.5
>
> Attachments: HCATALOG-598_fix_cmdline_version.1.patch
>
>
> As described in the [HCatalog release
> process|https://cwiki.apache.org/confluence/display/HCATALOG/HowToRelease]
> the project version number is always checked in with a {{-SNAPSHOT}} suffix.
> When producing release artifacts the release version is specified on the
> command-line. This seems reasonable as it prevents people from accidentally
> producing a snapshot jar labeled as a release.
> HCatalog switched to using maven for resolving dependencies and publishing
> artifacts, and during this change setting the version via the command-line
> broke. Unfortunately maven does not support setting the version via the
> command-line (see http://jira.codehaus.org/browse/MNG-624, which has ~300
> votes and ~200 watchers at this time). We need a mechanism to easily produce
> release artifacts and set the version on the command-line.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
