Cloud-Store SDK Maven Deployment Guide
This guide provides a step-by-step process for deploying a dependency to Maven Central Repository via OSS Sonatype.
Steps to Push a Dependency to a Maven Repository
Prerequisites:
Ensure you have the cloud-store-sdk-maven project directory, containing the necessary settings.xml and sunbird.asc files.
Steps:
Access the Repository:
Open your web browser and navigate to OSS Sonatype.
Login:
Use the username and password from the
cloud-store-sdk-maven/settings.xmlfile.
Generate a User Token:
After logging in, go to your profile.
From the profile drop-down menu, select User Token.
Click on Access User Token to generate a new username and token.
Update Maven Settings:
Add the newly generated username and token to your
settings.xmlfile.Copy the updated
settings.xmlfile to your.m2folder.
Deploy the Dependency:
Navigate to the directory
cloud-store-sdk_2.12.If you encounter GPG key errors, run:
If you receive an error related to GPG keys while deploying, follow these steps
Verify Deployment:
Open your browser and navigate to the Staging Repositories page to confirm your dependency has been pushed to the staging repository.
Release the Dependency:
Once confirmed, click the Release button to promote the dependency from the Staging Repository to Maven Central.
Managing GPG Keys
List Existing GPG Keys
To view all stored GPG keys and check for expiry:
Edit an Expired Key
If a key has expired, edit it as follows:
Replace
<KEY_ID>with the actual ID (e.g.,1FEE445AFBB262B5).Change Key Expiry
In the GPG interactive shell, type:
Provide the new expiration period when prompted.
Export the Updated Key
After updating, export the key:
Example:
gpg --armor --export 1FEE445AFBB262B5 > sunbird.ascImport an Updated GPG Key
To import the updated key:
Example:
gpg --import sunbird.asc
Last updated