Sign and Upload the release plugin zips to nexus maven release repo.

[prudhvigodithi]

Is your feature request related to a problem? Please describe

#1234

Describe the solution you'd like

settings.xml

<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
                      https://maven.apache.org/xsd/settings-1.0.0.xsd">
                    
  <servers>
    <server>
      <id>nexus</id>
      <username>${SONATYPE_USERNAME}</username>
      <password>${SONATYPE_PASSWORD}</password>
    </server>
  </servers>
</settings>

Create a staging repo nexus-staging:rc-open this will create a new new staging repository on the remote Nexus
Upload zips from the local filesystem to a staging repository using plugin in built deploy-staged-repository
Close the created staging repo nexus-staging:rc-close

• Sign the generate zips.
• Stage them as per staging repo workflow requirements.
• Add necessary tags in POM xml (modify before uploading) Example as

<licenses>
<license>
<name>The Apache License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
</license>
</licenses>
<developers>
<developer>
<id>amazonwebservices</id>
<organization>Amazon Web Services</organization>
<organizationUrl>https://aws.amazon.com</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:[email protected]:opensearch-project/common-utils.git</connection>
<developerConnection>scm:[email protected]:opensearch-project/common-utils.git</developerConnection>
<url>[email protected]:opensearch-project/common-utils.git</url>
</scm>
<dependencies/>

• Once verified publish to release repo.

[dblock]

Looks like a subset of #716

[prudhvigodithi]

Hey @dblock, there are two aspects for this maven publish, one for snapshots repo and other for actual release repo, the two repo workflows are not the same, as release repo has more wider process, like pre staging, promoting, signing, additional maven tags and then releasing, so I have created a meta issue #1916 that expands with more details based on the issue #716.

[prudhvigodithi]

Using the plugin opensearch.pluginzip and with existing CI worflows, the zips will signed and published
Example
https://repo1.maven.org/maven2/org/opensearch/plugin/opensearch-ml-plugin/2.0.1.0/
Closing this issue as resolved :)
@dblock @bbarani