So could someone please push the corrected metadata.xml to central?
Thanks, Craig
On Apr 1, 2009, at 7:16 PM, Craig L Russell wrote:Hi Brian, Apache JDO is responsible for maintaining the specification for JSR-243 and as such, manages the javax.jdo (specification) space as well as the org.apache.jdo (technology compatibility kit) space. The reference implementation is another open source project, DataNucleus http://www.datanucleus.org Hopes that clarifies it for you. Craig On Apr 1, 2009, at 6:24 PM, Brian E. Fox wrote:Curious. I would have expected it to be org.apache.jdo instead of javax. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, April 01, 2009 3:22 PM To: [email protected]; Carlos Sanchez Cc: Apache JDO project Subject: Re: M2 repo error Hi Brian, The Apache JDO project is officially in charge of the javax.jdo name space. And I'm acting on behalf of the Apache JDO project. Regards, Craig On Apr 1, 2009, at 12:07 PM, Brian E. Fox wrote:Shouldn't the jdo artifacts come to central directly from Sun? -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, March 31, 2009 8:13 PM To: Carlos Sanchez Cc: [email protected]; Apache JDO project Subject: Re: M2 repo error Hi Carlos, Can you please take a look at people.apache.org/repo/m2-ibiblio- rsync- repository/javax/jdo and verify that these artifacts (maven- metadata.xml, signature, checksum) look correct? If so, please push them to ibiblio. There should be only three versions: 2.0, 2.1, and 2.2. Thanks, Craig On Mar 20, 2009, at 9:17 AM, Carlos Sanchez wrote:Maybe you haven't got my message: It may have been auto generated at some point. If you use Maven 2 it will be generated. You can override it by putting a new one under http://people.apache.org/repo/m2-ibiblio-rsync-repository/ (and letting me know to setup an automatic sync) On Fri, Mar 20, 2009 at 9:14 AM, Craig L Russell<[email protected]wrote: Any ideas? Craig On Mar 16, 2009, at 10:43 AM, Craig L Russell wrote:Hi, I don't recall pushing this artifact to the repository; is it auto-generated perhaps? Any help in fixing it would be appreciated. Thanks, Craig still a mvn newbie Begin forwarded message:From: Andy Jefferson <[email protected]> Date: March 16, 2009 2:15:57 AM PDT To: [email protected] Subject: M2 repo error Reply-To: [email protected] Onhttp://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/there is a filehttp://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/maven-metadata.xmlwhich is presumably used by Maven(2) in determining what versions it is prepared to let the world know about. There is no 2.2 entry in it, nor 2.1 for that matter. Means that whenever anyone specifies to use "apache-jdo" (javax.jdo/jdo2-api) between 2.2 and 3.0 they get the really informative Couldn't find a version in [SNAPSHOT, 2.0-beta, 2.0-rc1, 2.0, 2.1-SNAPSHOT] to match range [2.2,3.0) javax.jdo:jdo2-api:jar:null Perhaps there's someone who can fix this ? Regards -- Andy (DataNucleus - http://www.datanucleus.org)Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!
Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
