CI pipeline update to publish geospatial-client jar

[andy-k-improving]

Description

To update the project setup, in order to publish geospatial-client jar for both snapshot and release version into aws.oss.sonatype.org during the CI execution with appropriate credential.

Related Issues

Resolves #698

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

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.

Testplan

# Publish the client Jar into local .m2 and examine the jar. 
gradle :geospatial-client:publishNebulaPublicationToMavenLocal 

[andy-k-improving]

@heemin32 I have checked on the existing pipeline, but I don't see any release logic for publishing production zip || jar.
Wonder is that published separately on AWS side?

[andy-k-improving]

@heemin32 @navneet1v Any thought?

[heemin32]

@heemin32 I have checked on the existing pipeline, but I don't see any release logic for publishing production zip || jar. Wonder is that published separately on AWS side?

Are you talking about something like this? https://github.com/opensearch-project/opensearch-build

[andy-k-improving]

@heemin32 yes, thanks for the reference, let me look into that.
In the meanwhile would that be possible to test this change on Github runner before merging?
Can we somehow trigger the build and publish snapshot workflow here, or we can only test it upon merging to main?

[heemin32]

@heemin32 yes, thanks for the reference, let me look into that. In the meanwhile would that be possible to test this change on Github runner before merging? Can we somehow trigger the build and publish snapshot workflow here, or we can only test it upon merging to main?

Not that I know of. I created a feature branch. feature/client we can merge it there to see how it works I guess.

https://github.com/opensearch-project/geospatial/actions/runs/12437060284

[martin-gaievski]

I'm seeing client jar as part of the zip for the plugin in aws maven repo: https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/geospatial/3.0.0.0-SNAPSHOT/. I think this is the desired behavior, but want to confirm that @andy-k-improving @heemin32

[andy-k-improving]

I'm seeing client jar as part of the zip for the plugin in aws maven repo: https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/geospatial/3.0.0.0-SNAPSHOT/. I think this is the desired behaviour, but want to confirm that @andy-k-improving @heemin32

Half half, the ideal state should be:

1. The client jar being part of the zip, so GeoSpatial plugin aware of it.
2. To have the geospatial-client jar distributed separately, so end user (Other OS plugin can be import it via Gradle).

# Gradle file for other OpenSearch plugin which wish to use the IP look up feature.
implementation ('org.opensearch:geospatial-client:3.0.0.0-SNAPSHOT')

Hence I reckon that's good to know we have the jar as part of the zip, but in this PR we are focusing to make sure the client-jar being published as a standalone jar for other project to import, if that make sense.

[andy-k-improving]

@heemin32 @martin-gaievski
Thanks both, I'm seeing the jar now published over to aws repo.
https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/geospatial-client/3.0.0.0-SNAPSHOT/

[heemin32]

@andy-k-improving Thank you for the contribution!