You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Nitay Joffe (JIRA)" <ji...@apache.org> on 2013/02/27 21:47:14 UTC

[jira] [Updated] (HIVE-4089) javax.jdo : jdo2-api dependency not in Maven Central

     [ https://issues.apache.org/jira/browse/HIVE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitay Joffe updated HIVE-4089:
------------------------------

    Description: The latest open source hive release (0.10.0) depends on javax.jdo artifact jdo2-api version 2.3-ec. This version is not actually in maven central, which means everyone who uses hive requires custom maven repository definitions which is discouraged by maven folks. I pinged the javax.jdo guys about it and they recommended we upgrade to 3.0. See http://goo.gl/fAoRn for the conversation.  (was: The latest open source hive release (0.10.0) depends on javax.jdo artifact jdo2-api version 2.3-ec. This version is not actually in maven central, which means everyone who uses hive requires custom maven repository definitions which is discouraged by maven folks. I pinged the javax.jdo guys about it and they recommended we upgrade to 3.0. See goo.gl/fAoRn for the conversation.)
    
> javax.jdo : jdo2-api dependency not in Maven Central
> ----------------------------------------------------
>
>                 Key: HIVE-4089
>                 URL: https://issues.apache.org/jira/browse/HIVE-4089
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Nitay Joffe
>            Assignee: Jarek Jarcec Cecho
>
> The latest open source hive release (0.10.0) depends on javax.jdo artifact jdo2-api version 2.3-ec. This version is not actually in maven central, which means everyone who uses hive requires custom maven repository definitions which is discouraged by maven folks. I pinged the javax.jdo guys about it and they recommended we upgrade to 3.0. See http://goo.gl/fAoRn for the conversation.

--
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