Provide convenience Maven "pom" artifacts for JDO/JPA usage

[GoogleCodeExporter]

Maven users would benefit from convenience "pom" artifacts. These are simply a 
way of defining a group of dependencies of required bits of software, so the 
user simply defines one dependency in their own POM. I would propose adding the 
following

datanucleus-appengine-jdo
datanucleus-appengine-jpa

See this link for one such example using DataNucleus+JDO+RDBMS

http://datanucleus.svn.sourceforge.net/viewvc/datanucleus/platform/accessplatfor
m/trunk/jdo-rdbms/pom.xml?revision=13935&view=markup

These then would be released into a Maven repository so that a user can just 
specify the following in their pom.xml

<dependency>
    <groupId>com.google.appengine.orm</groupId>
    <artifactId>datanucleus-appengine-jdo</artifactId>
    <version>2.0.0-RC2</version>
    <type>pom</type>
</dependency>

rather than the normal long list of different JDO, DataNucleus, AppEngine jars

Original issue reported on code.google.com by googleco...@yahoo.co.uk on 16 Dec 2011 at 1:36

[GoogleCodeExporter]

Sounds good to me. Which repo?

Original comment by max.r...@gmail.com on 18 Dec 2011 at 1:37

[GoogleCodeExporter]

Which Maven repo do Google place artifacts in normally ? I guess you use 
Sonatype and from there they get put in the Maven central repo

Original comment by googleco...@yahoo.co.uk on 18 Dec 2011 at 8:50

[GoogleCodeExporter]

See the two "projects" under "maven-appengine-artifacts" in SVN trunk. If you 
do "mvn clean install" these are available for use in your projects, so you 
just specify

<dependency>
    <groupId>com.google.appengine.orm</groupId>
    <artifactId>datanucleus-appengine-jdo</artifactId>
    <version>2.0.0-RC2</version>
    <type>pom</type>
</dependency>

in your projects pom.xml and it pulls in the relevant DN jars, plus 
jdo-api.jar, plus the datanucleus-appengine.jar. Give it a try and see what you 
think

Original comment by googleco...@yahoo.co.uk on 23 Dec 2011 at 9:28

[GoogleCodeExporter]

SVN trunk has these, so they just need deploying to the Maven repository each 
time a release is performed.

Original comment by googleco...@yahoo.co.uk on 1 Jan 2012 at 1:42

• Changed state: Fixed
• Added labels: TargetRelease-2.0

[GoogleCodeExporter]

Has the 2.0.0 release been pushed somewhere from which it will work its way 
into Maven Central? I can't find it at the moment.

Original comment by scottish...@googlemail.com on 1 Feb 2012 at 3:12