Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature] Publish ARCHIVE test distribution to Maven Local

See original GitHub issue

Describe the bug mavenLocalPublish Zip of OpenSearch Core repo doesn’t contain the core plugins(geo) present in the repo. This is leading to the failure of integration test on all the platforms(macOs, AmazonLinux2 etc).

To Reproduce Steps to reproduce the behavior:

Checkout the OpenSearch repo.
Run ./gradlew publishToMavenLocal -Dbuild.version_qualifier=beta1 -Dbuild.snapshot=false
Validate a zipfile is present in the path: ~/.m2/repository/org/opensearch/distribution/integ-test-zip/opensearch/3.0.0-beta1/
Checkout the out the geo-spatial repo from here: https://github.com/navneet1v/geospatial/tree/mavenLocalTesting
Then run ./gradlew integTest -PcustomDistributionUrl=“<path-to-opensearch-maven-local-zip>” example: ./gradlew integTest -PcustomDistributionUrl="/Users/navneev/.m2/repository/org/opensearch/distribution/integ-test-zip/opensearch/3.0.0-beta1/opensearch-3.0.0-beta1.zip"

Expected behavior The expectation is the integ Test should succeed.

Plugins None

Host/Environment (please complete the following information):

OS: macOs, AmazonLinux2
Version 11.6.5,

Impact This is impacting the ability to run the Integration test with the custom version of OpenSearch when as a developer you need to make changes in both the repos at same time.

Issue Analytics

State:
Created a year ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

navneet1vcommented, Jun 25, 2022

After discussing with @saratvemulapalli I was able to get an alternative way in which I can create the local TAR for the opensearch code. The idea was to use the commands provided here: https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#build to generate the tar for the specific platform. Once this is generated It can be easily accessed on this path: <OpenSearch-Repo-Path>/distribution/archives/darwin-tar/build/distributions/ and then use this path with the flag which I was already using -PcustomDistributionUrl with my integration tests. Volla, it worked.

Thanks @saratvemulapalli for providing me details around how I can access the tar.gz

Please feel free to resolve this issue. With the above solution we don’t need mavenlocal, but it will be good to have as first thing a developer look is the maven local for the artifacts created locally.

1reaction

saratvemulapallicommented, Jun 24, 2022

@navneet1v you should be able to build your own tarball using ./gradlew assemble. Take a look at: https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#build

Top Results From Across the Web

Maven Publish Plugin - Gradle User Manual

An aggregate task that publishes all defined publications to all defined repositories. It does not include copying publications to the local Maven cache....

Maven – Guide to uploading artifacts to the Central Repository

Guide to uploading artifacts to the Central Repository. In order for users of Maven to utilize artifacts produced by your project, you must...

Apache Maven Deploy Plugin – Usage

The Deploy Plugin has two basic functions. In most project builds, the deploy phase of the build lifecycle is implemented using the deploy: ......

Introduction to Repositories - Apache Maven

A repository in Maven holds build artifacts and dependencies of varying types. There are exactly two types of repositories: local and remote:.

Maven – Guide to deploying 3rd party JARs to remote repository

To deploy a 3rd party JAR use the deploy:deploy-file goal under maven-deploy-plugin. First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to ...