2.0.0-final not in maven repositories

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Look in http://www.datanucleus.org/downloads/maven2/ as reccomended by 
http://code.google.com/p/datanucleus-appengine/wiki/UpgradingToVersionTwo find 
there is no com/google and hence no com/google/appengine/orm
2. Look in 
http://google-maven-repository.googlecode.com/svn/repository/com/google/appengin
e/orm/datanucleus-appengine/ there are only version 1.0.0 and 1.0.1
3. Look on maven central the latest version listed is 1.0.10

What is the expected output? What do you see instead?
I expected to find version 2.0.0-final in maven central or failing that in 
google code or somewhat tediously only in the datanucleus repository. Instead I 
can't find it anywhere in an existing repository.

What version of the product are you using? On what operating system?
Trying to use 2.0.0-final on Linux Ubuntu with maven 3.

Please provide any additional information below.

Workaround: manually upload the jar files from the release zip into your 
locally hosted maven repository.

Original issue reported on code.google.com by scottish...@googlemail.com on 15 Feb 2012 at 10:38

[GoogleCodeExporter]

Assigned to Max since the issue is Google putting their plugins into Sonatype 
(from which they go into Maven central). The DataNucleus jars always get 
straight into Maven central the day after release by an automatic mechanism

Original comment by googleco...@yahoo.co.uk on 15 Feb 2012 at 11:29

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by googleco...@yahoo.co.uk on 28 Feb 2012 at 2:08

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Why is there a "2.0.0-RC3" in Maven central when this was never released.

Original comment by googleco...@yahoo.co.uk on 7 Mar 2012 at 1:46

[GoogleCodeExporter]

Is "2.0.0" supposed to be "2.0.0-final" ? if so, why does the POM file (in the 
repo) not reflect the dependencies that it is supposed to have ? The whole 
point of Maven integration and using a Maven repo is that such things are 
managed by Maven, and to do that you ought to put these things in the Maven 
repo using "deploy"

Original comment by googleco...@yahoo.co.uk on 2 Apr 2012 at 6:32

[GoogleCodeExporter]

So it looks like 2.0.0 has hit the maven central repositories which should 
close this bug. But Comment #4 is a valid new bug in that clearly 
com.google.appengine.orm:datanucleus-appengine:2.0.0 has dependencies but these 
are not specified. Currently working out which dependencies to specify in your 
pom file is horrible and consists of trying things and seeing what breaks. 
Specifying this correctly in the datanucleus-appengine pom file would make this 
so much better.

Original comment by scottish...@googlemail.com on 4 Apr 2012 at 3:02

[GoogleCodeExporter]

Could you please publish datanucleus-appengine-2.0.0-sources.jar at a maven 
repo too?
That helps a lot when debugging from eclipse IDE.

Original comment by luck...@gmail.com on 7 Apr 2012 at 6:04

[GoogleCodeExporter]

I see that 2.0.1 is now released ... and makes the same mistakes as all 
previous releases with respect to publishing a broken POM and no source jar.

Original comment by googleco...@yahoo.co.uk on 23 May 2012 at 3:16

[GoogleCodeExporter]

2.0.1.1 is the first release that is correctly placed in Maven with valid pom 
with dependencies, and with source jar. See 
http://repo1.maven.org/maven2/com/google/appengine/orm/datanucleus-appengine/2.0
.1.1/

Original comment by googleco...@yahoo.co.uk on 27 Jun 2012 at 6:06

• Changed state: Fixed