[
https://issues.apache.org/jira/browse/HIVE-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765555#comment-13765555
]
Brock Noland commented on HIVE-5107:
------------------------------------
Sounds good! After thinking about this for sometime I don't want to check any
svn mv commands into the branch. Therefore any patch to the maven branch which
would require:
1) (if moves where performed) add the commands to maven-rollforward.sh and
maven-rollback.sh
2) Execute maven-rollback.sh
3) Generate diff
4) After approval commit diff
Additionally when pulling from the branch we would:
1) Execute maven-rollback.sh
2) pull
3) Execute maven-rollforward.sh
4) Continue working
That is a little painful but it ensures we stay in-sync with trunk to as much
as possible.
> Change hive's build to maven
> ----------------------------
>
> Key: HIVE-5107
> URL: https://issues.apache.org/jira/browse/HIVE-5107
> Project: Hive
> Issue Type: Task
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: HIVE-5107-wip.patch
>
>
> I can not cope with hive's build infrastructure any more. I have started
> working on porting the project to maven. When I have some solid progess i
> will github the entire thing for review. Then we can talk about switching the
> project somehow.
--
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
