Yes, the changes to settings.xml helped. That got me past that issue. However, I ended up having some problems with the GPG side of things (GPG on Mac OSX) - similar to [1] so I couldn't close the stage repo. It seems like the artifacts were signed by a subkey which apparently doesn't work. So it looks like I need to do things over again. Does it harm doing mvn release:prepare and mvn release:perform a second time with the same version? I guess this will mean that the tag gets moved?
Cheers, David [1] https://issues.sonatype.org/browse/OSSRH-1525 On 21 March 2012 20:44, Sergey Beryozkin <sberyoz...@gmail.com> wrote: > Yes, this is what I did. > > David, I think we also need to get your public gpg key added to > http://pgp.mit.edu/, here are some links I found useful. > > http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/gpg-cs.html > > https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven > > You should be able to login to > https://repository.apache.org/index.html#welcome > > with your apache login/password, > > This guide is good: > http://www.apache.org/dev/publishing-maven-artifacts.html > > but this one on the Codehaus is also good: > http://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide > > HTH, thanks for deciding to give it a go :-) I'll get you a pint :-) > > Cheers, Sergey > > > > > On 21/03/12 20:34, Daniel Kulp wrote: >> >> >> David, >> >> Add to your ~/.m2/settings.xml something like: >> >> >> <settings> >> <servers> >> <server> >> <id>apache.releases.https</id> >> <username>dkulp</username> >> <password>yourapachepassword</password> >> </server> >> </servers> >> </settings> >> >> to setup your credentials needed to deploy to Nexus. If that works, let >> me >> know and I'll update the release page. (or feel free to update it) >> >> >> Dan >> >> >> >> On Wednesday, March 21, 2012 07:55:24 PM David Bosschaert wrote: >>> >>> On 21 March 2012 19:09, David Bosschaert<david.bosscha...@gmail.com> >> >> wrote: >>>> >>>> On 21 March 2012 15:34, Daniel Kulp<dk...@apache.org> wrote: >>>>> >>>>> If you are willing to do the release, then I think it's a good idea. >>>>> I'd >>>>> rather have a release often type thing if it fixes a few issue that are >>>>> needed. Do you know if it needs a new CXF proper release or is 2.5.2 >>>>> OK? If it's just a release of the DOSGi stuff, then it should be >>>>> pretty simple. I think a simple: >>>>> >>>>> mvn release:prepare >>>>> mvn release:perform >>>>> >>>>> should handle most of it. The release-manangement page for cxf >>>>> might >>>>> have more details about setting up the gpg stuff, Nexus, etc... >>>> >>>> >>>> It's the gpg and Nexus stuff that I'm unsure about in relation to how >>>> releases are done at Apache, but I see things are documented well on >>>> that page, so I'll give it a try soon. >>>> >>>> Cheers, >>>> >>>> David >>> >>> >>> I successfully completed the release:prepare (I think) but the >>> release:perform fails with the error below. >>> >>> Any ideas? Sergey, how did you do this before? >>> >>> David >>> >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 7.789s >>> [INFO] Finished at: Wed Mar 21 19:51:53 GMT 2012 >>> [INFO] Final Memory: 10M/81M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [WARNING] The requested profile "deploy" could not be activated because >>> it does not exist. >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy >>> (default-deploy) on project cxf-dosgi-ri: Failed to deploy artifacts: >>> Could not transfer artifact >>> org.apache.cxf.dosgi:cxf-dosgi-ri:pom:1.3.1 from/to >>> apache.releases.https >>> (https://repository.apache.org/service/local/staging/deploy/maven2): >>> Failed to transfer file: >>> >>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apac >>> he/cxf/dosgi/cxf-dosgi-ri/1.3.1/cxf-dosgi-ri-1.3.1.pom. Return code is: >>> 401 -> [Help 1] >>> ... more stuff ...
