Update build.gradle to include job-scheduler jar when staging maven publications.

[mch2]

Signed-off-by: Marc Handalian [email protected]

Description

• updates build.gradle to ensure the base jar has the required pom fields for publishing to maven central.
• updates to include this jar when publishing to the local staging repository currently used by CI to pick up artifacts for promotion.
• Updates developer on spi jar to be opensearch.
• Updates build.sh script to be in sync with the script in opensearch-build. The version of this script in this repo is a backup, a separate PR will be made to opensearch-build.

Issues Resolved

closes #114

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

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.

[mch2]

Not sure whats going on here with the build workflow. I'm getting the same thing locally. It should be pulling these deps from aws.oss, this repo has no reference to jcenter that I can see.

* What went wrong:
Execution failed for task ':compileTestJava'.
> Could not resolve all files for configuration ':testCompileClasspath'.
   > Could not resolve org.opensearch.test:framework:1.3.0-SNAPSHOT.
     Required by:
         project :
      > Could not resolve org.opensearch.test:framework:1.3.0-SNAPSHOT.
         > Unable to load Maven meta-data from https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml.
            > Could not get resource 'https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml'.
               > Could not GET 'https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

[saratvemulapalli]

Not sure whats going on here with the build workflow. I'm getting the same thing locally. It should be pulling these deps from aws.oss, this repo has no reference to jcenter that I can see.

* What went wrong:
Execution failed for task ':compileTestJava'.
> Could not resolve all files for configuration ':testCompileClasspath'.
   > Could not resolve org.opensearch.test:framework:1.3.0-SNAPSHOT.
     Required by:
         project :
      > Could not resolve org.opensearch.test:framework:1.3.0-SNAPSHOT.
         > Unable to load Maven meta-data from https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml.
            > Could not get resource 'https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml'.
               > Could not GET 'https://jcenter.bintray.com/org/opensearch/test/framework/1.3.0-SNAPSHOT/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Yup the repo doesn't have Jcenter configured, do you think its being pulled by ShadowPlugin?

[mch2]

related - opensearch-project/opensearch-build#1456

[mch2]

Looks like the changes to Opensearch 1.x fix the build, I no longer see Bintray as a repo option.

2022-01-13T09:32:11.407-0800 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver] Attempting to resolve component for org.apache.httpcomponents:httpcore-nio:4.4.12 using repositories [MavenRepo, MavenRepo2, opensearch-downloads, opensearch-downloads2, opensearch-snapshots, elasticsearch-downloads, elasticsearch-snapshots, MavenLocal, MavenRepo3, maven]