You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As part of the effort, to migrate the generated plugin zips to maven, I have created a java custom gradle plugin, so that downstream repos can apply the plugin during the distribution build. Example as apply plugin: 'opensearch.zippublish', once applied the generated zips should be published to maven repo. I see the OpenSearch already has some custom plugins to avoid reusability, the same way I have added a custom java plugin as shown in the PR, but when I try to run the manifest file I dont see this custom plugin gets added to local maven repo for the the components to use this and throws
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* Where:
Build file '/tmp/tmpkn5redc4/job-scheduler/build.gradle' line: 33
* What went wrong:
A problem occurred evaluating root project 'opensearch-job-scheduler'.
> Plugin with id 'opensearch.zippublish' not found.
Just to summarize the plugin functionality works fine as expected, just the pending part is how to integrate with the existing custom plugin setup, so that even this is added to local maven repo during runtime and each component can then use it.
To Reproduce
Steps to reproduce the behavior:
Add the custom gradle java plugin to this location
apply plugin: 'opensearch.zippublish' to any the plugin components Ex job-scheduler
Run ./build.sh manifests/2.0.0/opensearch-2.0.0.yml --snapshot --component job-scheduler
Expected behavior
The expected behavior is to identify the applied plugin and proceed to execute the plugin functionality.
Screenshots
The text was updated successfully, but these errors were encountered:
Hey @dblock yes, the issue is resolved,
So my plugin gets added to build-tools (that has a particular version), but in build.gradle, it points to wrong build-tools version. hence it throws the error as Plugin with id 'opensearch.zippublish' not found.
If I point to right build-tools version
Example as
classpath "org.opensearch.gradle:build-tools:${opensearch_version}"
to
classpath "org.opensearch.gradle:build-tools:2.0.0-alpha1-SNAPSHOT
Describe the bug
As part of the effort, to migrate the generated plugin zips to maven, I have created a java custom gradle plugin, so that downstream repos can apply the plugin during the distribution build. Example as
apply plugin: 'opensearch.zippublish'
, once applied the generated zips should be published to maven repo. I see the OpenSearch already has some custom plugins to avoid reusability, the same way I have added a custom java plugin as shown in the PR, but when I try to run the manifest file I dont see this custom plugin gets added to local maven repo for the the components to use this and throwsJust to summarize the plugin functionality works fine as expected, just the pending part is how to integrate with the existing custom plugin setup, so that even this is added to local maven repo during runtime and each component can then use it.
To Reproduce
Steps to reproduce the behavior:
apply plugin: 'opensearch.zippublish'
to any the plugin components Ex job-scheduler/build.sh manifests/2.0.0/opensearch-2.0.0.yml --snapshot --component job-scheduler
Expected behavior
The expected behavior is to identify the applied plugin and proceed to execute the plugin functionality.
Screenshots

The text was updated successfully, but these errors were encountered: