hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] [Commented] (HIVE-4089) javax.jdo : jdo2-api dependency not in Maven Central
Date Wed, 03 Jul 2013 16:22:20 GMT


Ashutosh Chauhan commented on HIVE-4089:

DN author [~andy] comments on mail thread above is worth considering.
> "jdo2-api-2.3-ec" was an artifact created by DataNucleus as a temporary
> measure so that we could continue to provide new features for things that
> were
> not officially released on Apache JDO (due to the time it was taking to
> get an
> official release).
> I can't see how Apache JDO can push something to Maven Central when they
> didn't provide it in the first place. You would be better advised to
> upgrade
> your project to use "jdo-api-3.0.jar" which was released 2 years ago and
> superceded "v2.3-ec" and _likely_ would be compatible.

In light of this I strongly believe we should upgrade to 3.0.1 
[~appodictic] If you test it as you suggested above and find out that for some arcane reason
our current version 2.3-ec turns out to be better than 3.0.1 even in that case since 2.3-ec
is not a supported version, if there are bugs or other issues in future we need to upgrade
than. Since we already have 1 issue at hand, I think we should upgrade now. What do you think?
> javax.jdo : jdo2-api dependency not in Maven Central
> ----------------------------------------------------
>                 Key: HIVE-4089
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Nitay Joffe
>            Assignee: Jarek Jarcec Cecho
>         Attachments: HIVE-4089.D11253.1.patch
> 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
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:

View raw message