-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish plugin zips to maven repo #175
Comments
@kkhatua @sruti1312 Can you please make the necessary changes as listed on the document to support publishing your zips to Maven? |
@prudhvigodithi Not integrated yet. I will plan to raise the PR by today/tomorrow. |
@prudhvigodithi @bbarani I don't think we need to do this for performance-analyzer-rca package as this is not a plugin and runs as a separate process within cluster. |
Hey @sgup432, make sense, if the component distribution output is not a zip, then |
@kkhatua Hey, what's the latest on this? Do you have an ETA? |
@prudhvigodithi @CEHENKLE So these changes are not needed for this. Closing. |
Description
With existing setup the plugin jars are only published to maven repo, but not the generated plugin zips.
Related META issue
opensearch-project/opensearch-build#1916
Current Behavior
Existing all maven publications target the jar files to publish to maven, but not the generated distribution zips.
Expected Behavior
Along with plugin jars, plugin zips should also be published to maven repo with right maven coordinates, so user can download these plugins using dependancy model.
Steps To Reproduce
Proposed solution
A custom gradle plugin solution that can create the publication task for the zips to get published to local staging maven repo with right maven coordinates.
Add/Configure the custom gradle plugin openseearch.pluginzip to the gradle project and test the generated plugin zip's to upload to local maven repo.
More details on how to use the Plugin:
https://github.com/opensearch-project/opensearch-plugins/blob/main/BUILDING.md#opensearchpluginzip
The text was updated successfully, but these errors were encountered: