[jira] [Commented] (SPARK-4914) Two sets of datanucleus versions left in lib_managed after running dev/run-tests

["Apache Spark (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255203#comment-14255203 ] 

Apache Spark commented on SPARK-4914:
-------------------------------------

User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/3756

> Two sets of datanucleus versions left in lib_managed after running dev/run-tests
> --------------------------------------------------------------------------------
>
>                 Key: SPARK-4914
>                 URL: https://issues.apache.org/jira/browse/SPARK-4914
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.2.0
>            Reporter: Cheng Lian
>            Priority: Minor
>
> The {{dev/run-tests}} script first does a clean compile with Hive 0.12.0, and then builds assembly jar for unit testing with Hive 0.13.1 *without* cleaning. This left two sets of datanucleus jars under the {{lib_managed}} folder, one set depended by Hive 0.12.0, another by Hive 0.13.1.
> This behavior sometimes messes up class paths and makes {{CliSuite}} and {{HiveThriftServer2Suite}} fail, because these two suites spawn external processes that depends on those datanucleus jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org