Push to Maven central

[GoogleCodeExporter]

Please push to library to Maven central.

If you require some help let me know.
I will be pushing the objectify-appengine-spring library also to Maven central 
using the Sonatype OSS repo.

Original issue reported on code.google.com by marceloverdijk on 9 Nov 2010 at 8:15

[GoogleCodeExporter]

Yes, you are welcome to push up the artifacts to maven central.

From what I understand most of the pushing to maven central is all manual. If 
there is some way to easily automate it from our ant build script we would be 
willing to add that into the build process.

Original comment by scotthernandez on 1 Jan 2011 at 5:47

• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

Matt, you can do whatever you want with this issue :-)

Original comment by lhori...@gmail.com on 8 May 2011 at 11:25

[GoogleCodeExporter]

Have a look at 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide . The process is almost completely scriptable from both Maven and Ant.

Original comment by robert.munteanu on 9 May 2011 at 10:38

[GoogleCodeExporter]

Yup - sonatype is the way to go. You basically just have to create the ticket 
with them, and you'll be up in about a day and auto-synced from that point on. 
Super useful for both releases and snapshops, and the users don't have hit a 
completely separate repo all the time just for this.

Original comment by adamf...@gmail.com on 31 Jan 2012 at 12:31

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This issue can be closed as version 4+ artifacts are pushed to Maven Central.

Original comment by mar...@overdijk.me on 14 Jul 2013 at 8:10

[GoogleCodeExporter]

Good point!

Original comment by lhori...@gmail.com on 14 Jul 2013 at 3:16

• Changed state: Fixed