[
https://issues.apache.org/jira/browse/HIVE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235272#comment-15235272
]
Sergio Peña commented on HIVE-12033:
------------------------------------
[~ashutoshc] Agree. There are some things that are failing due to
HIVE_TEST_CLASSPATH not being generated with these changes.
This is the variable on the pom.xml that is empty on these changes:
{code}
...
<test.hive.hadoop.classpath>${maven.test.classpath}</test.hive.hadoop.classpath>
...
{code}
maven.test.classpath is an ANT variable, and test.hive.hadoop.classpath is
needed by all TestCliDrivers to run the tests. So, no ANT, no classpath. But
everything runs OK in IntelliJ.
However, just last week I learned about 'depenency:build-classpath', so it
might be good to investigate how to get the classpath using code of the
build-classpath goal. If you have some ideas, it would be the last piece to
make this works.
> Move TestCliDriver/TestNegativeCliDriver out of ANT and make it debugable
> -------------------------------------------------------------------------
>
> Key: HIVE-12033
> URL: https://issues.apache.org/jira/browse/HIVE-12033
> Project: Hive
> Issue Type: Improvement
> Components: Test
> Affects Versions: 1.2.1
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Minor
> Attachments: HIVE-12033.1-spark.patch, HIVE-12033.1.patch
>
>
> The ANT auto-generated test sources make TestCliDriver code a little
> complicated to debug with IntelliJ and Eclipse. Remote debugging is the best
> choice to do it.
> There must be a new way to move out the ANT auto-generated source plug-in,
> and make TestCliDriver easy debuggable by current IDE, such as IntelliJ and
> Eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
