search

google-code-export / morphia

Automatically exported from code.google.com/p/morphia
1 stars 0 forks source link

Deploy Morphia to maven central #291

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Dear developers, 

great project but you'd reach even more developers if you'd deploy your project 
to maven central. It's quite easy and doesn't take any longer than the normal 
release build. I just don't like a bunch of single artifact repos in my pom.xml
Have a look here: 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide

Best Regards,
Sebastian

Original issue reported on code.google.com by Sebastian.Annies on 29 Jun 2011 at 3:27

GoogleCodeExporter commented 9 years ago 
This has come up before and I'm happy see it go up there but I don't have the 
time or inclination to do it myself. If a volunteer wants to help out, that 
would be great.

Original comment by scotthernandez on 29 Jun 2011 at 3:42

GoogleCodeExporter commented 9 years ago

Original comment by scotthernandez on 29 Jun 2011 at 3:47

GoogleCodeExporter commented 9 years ago 
Me!

I'll attach a patch. 

But then you will need to sign up at sonatype jira: 

https://issues.sonatype.org/browse/OSSRH so

 that you get a login on their Nexus instance.

Original comment by Sebastian.Annies on 29 Jun 2011 at 3:51

GoogleCodeExporter commented 9 years ago 
Just to be clear, once i sign up I will not have to do anything special when we 
do releases? It will all be automated?

The problem I've come up to in the past has been to require me to manually 
create an issue to upload each release to the repo; I do not want to do that.

Original comment by scotthernandez on 29 Jun 2011 at 3:56

GoogleCodeExporter commented 9 years ago 
No one wants extra-work. I understand that ;) 

The releases are uploaded into a staging repository. You will have to 'close & 
release' that staging repo to make the artifacts finally available to the 
public. 

'close & release' is one extra step: Log into the Nexus UI at 
https://oss.sonatype.org/index.html and hit two buttons if the release was ok. 
This process is required to be sure no half-released(deploy breaks after some 
modules are already deployed) projects are synced to repo1.

This is to be done on every release. 

Before the first release you will also need GPG key to sign the artifacts. 

Hope that is not too much work. Nevertheless I'll attach a patch. Just have a 
look.

Original comment by Sebastian.Annies on 29 Jun 2011 at 4:08

GoogleCodeExporter commented 9 years ago 
Step 1 remove the org.reflections dependency as this lib is not available on 
central (You may not point outside of central)

Step 2 adds a release profile that creates GPG signatures. (see: 
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With
+Maven)

The video shows what you have to do after the regular release (manual step). 

Best regards,
Sebastian

Original comment by Sebastian.Annies on 29 Jun 2011 at 5:42

Attachments:

GoogleCodeExporter commented 9 years ago 
Shall I update the patches or don't you plan to release to central?

Original comment by Sebastian.Annies on 9 Jan 2012 at 10:42