...

1. You have an account with commit access for the vivo-project on github. As a committer, you should already have this level of access.
2. You have an account with edit privileges on the lyrasis.org Confluence wiki.
3. You have an oss.sonatype.org account with generated token and have requested to be given permission to publish to the org.vivoweb groupId by adding a comment to the the VIVO Sonatype Hosting Ticket
4. You have project configuration privileges on JIRA (you'll see an error here if you don't) : must be added to `Project Settings → Administrators` role

...

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <profiles>
    <id>ossrh</id>
    <activation>
      <activeByDefault>true</activeByDefault>
    </activation>
    <properties>
       <gpg.keyname>YourKeyID</gpg.keyname>
       <gpg.passphrase>YourKeyPassphrase</gpg.passphrase>
       <gpg.defaultKeyring>false</gpg.defaultKeyring>
       <gpg.useagent>true</gpg.useagent>
       <gpg.lockmode>never</gpg.lockmode>
       <gpg.homedir>YourGPGDir</gpg.homedir>
       <gpg.publicKeyring>YourGPGDir/pubring.gpg</gpg.publicKeyring>
       <gpg.secretKeyring>YourGPGDir/secring.gpg</gpg.secretKeyring>
    </properties>
  </profiles>
  <servers>
    <!--Login info for Sonatype SnapShot repository-->
    <server>
      <id>ossrh</id>
      <username>YourSonatypeUsername<<username>YourSonatypeToken</username>
      <password>YourSonatypePassword</password>
    </server>
	<server>
      <id>sonatype-nexus-snapshots</id>
      <username>YourSonatypeUsername<<username>YourSonatypeToken</username>
      <password>YourSonatypePassword</password>
	</server>
    <server>
      <id>github</id>
      <username>your-github-id</username>
      <password>your-github-pwd</password>
    </server>
  </servers>
</settings>

...

• Checkout VIVO-release-publishing project (git checkout https://github.com/vivo-project/VIVO-release-publisher)
• Configure variables for creation of release candidate (defineVariables.sh)

  
  

  Code Block
  title Variable release number
  #!/bin/bash # RC define common variables Script export RC_TARGET_DIR=RC export ORG=vivo-project export PERSONAL_ACCESS_TOKEN=XXXXXXXX export BRANCH=main export RC_VERSION=1.14.0 export RC_VERSION_MINOR=1.14 export RC_NEXT_SNAPSHOT=1.14.1 RC_NUM=5 export Vitro_REPO=Vitro export Vitro_TAG=vitro export Vitro_RC_NUM=${RC_NUM} export VIVO_REPO=VIVO export VIVO_TAG=vivo export VIVO_RC_NUM=${RC_NUM}

  
  

• run publishReleasepublishReleaseVitro.sh (./publishReleasepublishReleaseVitro.sh)
• Go to https://github.com/vivo-project/Vitro/releases/ and check if everything is ok

• Go to https://oss.sonatype.org/index.html (Nexus Repository Manager)
• Click on Log In (Top Right Corner) and use your ossrh id from your settings.xml file

• Click Staging Repositories in left navigation under Build Promotion which will open a new tab

• Search for "vivoweb" in upper right search box (project will not have $REPO in title)

• Select repository and verify that Vitro is present in the Content tab
  • Look for the correct types as well - war, pom, jar, md5, asc, etc.
    • Note there is sometimes a delay on larger files showing in the Repo.
• Click Close, then Refresh, then Release
• After a few moments click into the search under Artifact Search in the left navigation and type "vivoweb"
• A new Search tab will appear with all of the org.vivoweb Release artifacts
• Verify that the new release versions are now listed
  • Note there is sometimes a delay on larger files showing in the Repo.
• This will publish the artifacts to the Sonatype releases repository and start the process of syncing them with Maven Central, which may take several hours. When finished, they'll be available at https://repo1.maven.org/maven2/org/vivoweb.

• Wait until the Vitro release is available in the maven repository (http://repo1.maven.org/maven2/org/vivoweb). This make take several hours or one day.
• run publishReleaseVIVO.sh (./publishReleaseVIVO.sh)
• Go to https://github.com/vivo-project/VIVO/releases/ and check if everything is ok
• Go to https://oss.sonatype.org/index.html (Nexus Repository Manager)
• Click on Log In (Top Right Corner) and use your ossrh id from your settings.xml file

• Click Staging Repositories in left navigation under Build Promotion which will open a new tab

• Search for "vivoweb" in upper right search box (project will not have $REPO in title)

• Select repository and verify that $REPO VIVO is present in the Content tab
  • Look for the correct types as well - war, pom, jar, md5, asc, etc.
    • Note there is sometimes a delay on larger files showing in the Repo.
• Click Close, then Refresh, then Release
• After a few moments click into the search under Artifact Search in the left navigation and type "vivoweb"
• A new Search tab will appear with all of the org.vivoweb Release artifacts
• Verify that the new release versions are now listed
  • Note there is sometimes a delay on larger files showing in the Repo.
• This will publish the artifacts to the Sonatype releases repository and start the process of syncing them with Maven Central, which may take several hours. When finished, they'll be available at https://repo1.maven.org/maven2/org/vivoweb.
• Make release announcement and update technical documentation at wiki
• Distribute the message that new release has been published

Push Release Branch to develop and Maintenance

...