db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Adams <matt...@matthewadams.me>
Subject Re: Deploying javax.jdo:jdo2-api:2.3-ec to maven central
Date Fri, 22 Feb 2013 20:21:58 GMT
I was saying that I don't see a problem with uploading jdo2-api to Maven
Central.  Who released it seems a minor consideration, since effectively,
Apache now has the bits.

I'm just trying to be practical and lower friction.  We need as little
impedance to use as possible, IMHO.


On Fri, Feb 22, 2013 at 1:26 PM, Craig L Russell
<craig.russell@oracle.com>wrote:

> Hi Matthew,
>
> On Feb 22, 2013, at 6:20 AM, Matthew Adams wrote:
>
>  Actually, see
>> http://search.maven.org/#**artifactdetails%7Cjavax.jdo%**
>> 7Cjdo-api%7C3.0.1%7Cjarfor<http://search.maven.org/#artifactdetails%7Cjavax.jdo%7Cjdo-api%7C3.0.1%7Cjarfor>
>>
>>
>> <dependency>
>>     <groupId>javax.jdo</groupId>
>>     <artifactId>jdo-api</**artifactId>
>>     <version>3.0.1</version>
>> </dependency>
>>
>> is the latest, likely compatible, but I don't see why a retroactive
>> release of the last version of jdo2-api could be uploaded to maven
>> central.
>>
>
> The phrasing of this sentence leaves a bit to be desired, so I can't
> really tell what you mean.
>
> I agree with Andy that the JDO project should not upload to maven central
> an artifact that was not released by the project.
>
> Craig
>
>>
>>
>> On Fri, Feb 22, 2013 at 2:10 AM, Andy Jefferson <andy@datanucleus.org
>> >wrote:
>>
>>  We have a few projects that depend on jdo2-api version 2.3-ec. For
>>>>
>>> example
>>>
>>>> hive:
>>>>
>>>>  http://search.maven.org/#**artifactdetails%7Corg.apache.**
>>> hive%7Chive-metastore<http://search.maven.org/#artifactdetails%7Corg.apache.hive%7Chive-metastore>
>>>
>>>> %7C0.10.0%7Cjar It seems that this artifact is not in central:
>>>>
>>>>  http://search.maven.org/#**search%7Cgav%7C1%7Cg%3A%**
>>> 22javax.jdo%22%20AND%20a%3
>>>
>>>> A%22jdo2-api%22
>>>> This requires users to put in special repository definitions to get that
>>>>
>>> one
>>>
>>>> artifact, which is discouraged by maven folks. Can you guys push it to
>>>> central?
>>>>
>>>
>>> "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.
>>>
>>>
>>> Regards
>>> --
>>> Andy
>>> DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)
>>>
>>>
>>
>>
>> --
>> mailto:matthew@matthewadams.me <matthew@matthewadams.me>
>>
>> skype:matthewadams12
>> googletalk:matthew@**matthewadams.me<googletalk%3Amatthew@matthewadams.me>
>> http://matthewadams.me
>> http://www.linkedin.com/in/**matthewadams<http://www.linkedin.com/in/matthewadams>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.**com <Craig.Russell@oracle.com>
> P.S. A good JDO? O, Gasp!
>
>


-- 
mailto:matthew@matthewadams.me <matthew@matthewadams.me>
skype:matthewadams12
googletalk:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message