...
- Good Ant tutorial: http://i-proving.ca/space/Technologies/Ant+Tutorial
Hadoop Dependencies
The Hive build downloads a number of different Hadoop versions via ivy in order to compile "shims" which allow for compatibility with these Hadoop versions. However, by default, the rest of Hive is only built and tested against a single Hadoop version (0.20.1 as of this writing, but check build.properties for the latest).
...
- When creating a review request you should select the "hive" repository and enter "trunk" in the "Base Directory" field (note that this value is interpreted relative to "http://svn.apache.org/repos/asf/hive/").
- If you're using Git instead of svn, you will need to select the
hive-gitrepository.
- If you're using Git instead of svn, you will need to select the
- Add the JIRA ID to the Bugs field, e.g. "HIVE-1212".
- Add "hive" to the "Groups" field.
- This ensures that Review Board will send a notification email to the hive-dev list.
- Use JIRA name and the short title for the "Summary" Field (eg: HIVE-1234: fix X Y Z)
- You will need to click on the Publish button after you make a change.
- Please add a comment to the JIRA ticket with a link to your review request.
- Use the Hadoop's code review checklist as a rough guide when doing reviews
- Reviewers can approve the patch by clicking on the "Ship it" option.
- Should your patch earn a -1 review, set the issue status to 'Resume Progress', upload a patch to Review Board with necessary fixes and then set the status to 'Submit Patch' again.
...
Finally, patches should be attached to an issue report in JIRA via the Attach File link on the issue's JIRA. Please add a comment that asks for a code review following our code review checklist. Please note that the attachment should be granted license to ASF for inclusion in ASF works (as per the Apache License §5).
When you believe that your patch is ready to be committed, select the Submit Patch link on the issue's JIRA.
...