New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First release to sonatype #35
Comments
@guerda I'm having trouble finding the (2?) maven commands to create the release now (they're in a ticket or PR, but I've lost track of which one). When I ran those, the first step failed part way through, but it was able to tag the release (and pushed that to github...) It failed during some of the signing process because I didn't have that set up locally, and it didn't seem to recover properly, but it was far enough along that I couldn't make progress on either command. I should try again, if you could post the commands again here. (Long story -- I had to repave my machine this week, so I'm in a different state, but most things should be restored from backups.) |
mvn release:prepare prepares the release in that way that the tag is created in SCM and your pom is ready for the next version. If you want to test the preparation without tagging the version in SCM, you can append -DdryRun=true. More details on mvn release:prepare |
Thanks! I'm still having issues, though. It may be easiest to just bump to 1.0.1-SNAPSHOT and release that... Here's what happens, using master from the github repo:
|
Ok, I restored the old repo workspace I was on, deleted the tag, and got through
|
Ok, I think I did a snapshot deployment with |
I'm not sure that you have to specify the developerConnection via -DconnectionUrl= because it should be defined correctly in the pom.xml. |
I did -- this is the error I see:
|
I'm too busy in the work now but I can try it in June. Anyway I think that @guerda has more experience with this than me (that I have 0 experience with maven), so he should take it (if he want to). |
I will try and look into it. I cannot say anything definitely yet. I will try :) |
CJWizard is now deployed to "Bintray JCenter" (https://bintray.com/bintray/jcenter), an alternative for "maven central". See also #14. It's located here: https://bintray.com/cjwizard/CJWizard/cjwizard Do you insist to have it also in "maven central"? Otherwise we could close this "old" issue. Best regards, |
Yes I think it's enough. El lun, 14 de noviembre de 2016 21:21, Peti Koch notifications@github.com Hello @guerda https://github.com/guerda and @PhoneixS CJWizard is now deployed to "Bintray JCenter" ( It's located here: https://bintray.com/cjwizard/CJWizard/cjwizard Do you insist to have it also in "maven central"? Otherwise we could close this "old" issue. Best regards, — |
I think is time to release to the maven repository as the ticket that was opened (https://issues.sonatype.org/browse/OSSRH-14241) was closed as Fixed.
This have to be done by @creswick as I think is who have the rights to do it. You can see how to do it with http://central.sonatype.org/pages/releasing-the-deployment.html.
This is needed to close #14 finally.
The text was updated successfully, but these errors were encountered: