File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 7777 if the release looks good. You can download uploaded artifacts from there.
7878 How to manually test a staged release is explained
7979 [ here] ( https://central.sonatype.org/publish/publish-portal-api/#manually-testing-a-deployment-bundle )
80- - publish the new release
80+ - create a bearer token as described [ here] ( https://central.sonatype.org/publish/publish-portal-api/#authentication-authorization )
81+ - add the sections mentioned [ here] ( https://central.sonatype.org/publish/publish-portal-api/#maven )
82+ using the bearer token you created in the previous step to your ` ~/.m2/settings.xml `
83+ - clone the jgit-build-test repo from github
84+ ```
85+ $ git clone https://github.com/msohn/jgit-build-test
86+ ```
87+ - update the version in its `pom.xml` to the new JGit release you staged
88+ - delete all jgit artifacts from your local m2 repository
89+ ```
90+ $ rm -r ~/.m2/org/eclipse/jgit
91+ ```
92+ - build the jgit-built-test maven project to test if all artifacts of the new release
93+ can be downloaded and used in a build
94+ ```
95+ $ mvn clean install -Pcentral.manual.testing
96+ ```
97+ - commit the version update in jgit-build-test and push it to github
98+ - if the test build of jgit-build-test succeeded publish the new release
8199 - by clicking "Publish" on the [portal deployment page](https://central.sonatype.com/publishing/deployments)
82100 - or by running
83101 ```
84102 $ JRELEASER_MAVENCENTRAL_STAGE=PUBLISH jreleaser deploy
85103 ```
104+ - when publication finished check if the new version is available
105+ on [Maven Central](https://repo1.maven.org/maven2/org/eclipse/jgit/)
You can’t perform that action at this time.
0 commit comments