Fix publishing

[ryanbogan]

Description

Fixes publishing to Maven and Sonatype that was broken by #687

Issues Resolved

#798

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dbwiddis]

OK to try this... but are we losing information in that generated POM?

[ryanbogan]

I thought that the POM would still generated, but it's just by opensearchplugin instead. @owaiskazi19 do you know if that's right?

[owaiskazi19]

I thought that the POM would still generated, but it's just by opensearchplugin instead. @owaiskazi19 do you know if that's right?

Can you test using: https://github.com/opensearch-project/opensearch-plugins/blob/main/WORKFLOWS.md#testing if the POM file is generated on your local?

[ryanbogan]

@dbwiddis @owaiskazi19 opensearch-sdk-java-2.0.0-SNAPSHOT.pom is generated in the .m2 folder

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.x 1.x
# Navigate to the new working tree
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-800-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 fbe2b9fcf2aaa79d8c63f27683ef28a3206418e9
# Push it to GitHub
git push --set-upstream origin backport/backport-800-to-1.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-800-to-1.x.