[ 
https://issues.apache.org/jira/browse/HIVE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886158#action_12886158
 ] 

HBase Review Board commented on HIVE-1453:
------------------------------------------

Message from: "Carl Steinbach" <c...@cloudera.com>

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/280/
-----------------------------------------------------------

(Updated 2010-07-07 16:48:34.380890)


Review request for Hive Developers.


Summary
-------

Modified launch configurations to use parameterized version from build 
configuration instead of hardcoding specific versions.


This addresses bug HIVE-1453.
    http://issues.apache.org/jira/browse/HIVE-1453


Diffs
-----

  eclipse-templates/HiveCLI.launchtemplate 83b5195 
  eclipse-templates/TestCliDriver.launchtemplate 8833251 
  eclipse-templates/TestHive.launchtemplate 4d740ad 
  eclipse-templates/TestJdbc.launchtemplate 2f75b17 
  eclipse-templates/TestMTQueries.launchtemplate d21b579 
  eclipse-templates/TestTruncate.launchtemplate fcde6b8 

Diff: http://review.hbase.org/r/280/diff


Testing
-------

Executed all launch configurations - they now seem to work as expected.


Thanks,

Arvind




> Build configuration changes introduced regression in launch configurations
> --------------------------------------------------------------------------
>
>                 Key: HIVE-1453
>                 URL: https://issues.apache.org/jira/browse/HIVE-1453
>             Project: Hadoop Hive
>          Issue Type: Bug
>         Environment: All Eclipse environments
>            Reporter: Arvind Prabhakar
>            Assignee: Arvind Prabhakar
>         Attachments: HIVE-1453.patch
>
>
> The changes to prepare for branching out 0.6.0 required [changes to build 
> configuration|http://svn.apache.org/viewvc/hadoop/hive/trunk/build.properties?r1=952877&r2=956430]
>  which caused the launch configurations to break as the jars they referred to 
> were renamed automatically. As a result, none of the launch configurations 
> are working at this point.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to