[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841600#action_12841600
]
Gerrit Jansen van Vuuren commented on HIVE-1095:
------------------------------------------------
What I said was a bit confusing I've realized :) and what I meant was:
There are two parts:
-> Commiting (if reviewed and accepted) the HIVE-1095-trunk.patch to the
trunk. This is generated against trunk.
-> Using the HIVE-1095-0.4.1.patch against the version 0.4.1 of hive to
generate the maven artifacts for 0.4.1 hive, are commits allowed for already
versioned releases? if so then it would be better to have it committed cause
any changes to build.xml, ivy.xml or build-common.xml would mean that the patch
needs generation.
So the broad scope and idea would be to publish the already released hive
versions to the maven repo:
0.3.0
0.4.0
0.4.1
0.5.0
and then have the build in trunk so that when another release is made the maven
publishing code is already in the build and its only needed to run ant
maven-publish.
By writing this I've realized that I probably need to generate the patches for
the builds on the other versions of hive also, should I do this and attach to
this task?
> Hive in Maven
> -------------
>
> Key: HIVE-1095
> URL: https://issues.apache.org/jira/browse/HIVE-1095
> Project: Hadoop Hive
> Issue Type: Task
> Components: Build Infrastructure
> Affects Versions: 0.6.0
> Reporter: Gerrit Jansen van Vuuren
> Priority: Minor
> Fix For: 0.6.0
>
> Attachments: HIVE-1095-0.4.1.patch, HIVE-1095-Sample.patch,
> HIVE-1095-trunk.patch
>
>
> Getting hive into maven main repositories
> Documentation on how to do this is on:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
