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
The OpenSearch project publishes all of the opensearch modules and Opensearch-project-provided plugins to maven central.
This allows some users of opensearch to embed opensearch in their own JVM applications, loading plugins directly via custom dependency management and build tools e.g. maven, sbt, gradle, leiningen, ...; and injecting the plugin classes directly into OpenSearch Node instances.
would it be feasible to publish this plugin as an artifact to the io.aiven org on mvnrepository?
This would allow us a internally "compliant" way to take this to production.
The text was updated successfully, but these errors were encountered:
@adityachadha-tomtom Thanks for creating the ticket, I think it is duplication of #64 – that ticket has a long history in comments, just check out the latest comments at the bottom of the page to see the latest status.
@adityachadha-tomtom Thanks for creating the ticket, I think it is duplication of #64 – that ticket has a long history in comments, just check out the latest comments at the bottom of the page to see the latest status.
i don't think that it's the same: my issue is specifically about publishing the ZIP file while this issue here seems to be about publishing the JAR files & co. (i.e. "normal" maven publishing of a java lib). the two issues are complementary (and when implementing #64 i guess this here comes more-or-less along for free)
The OpenSearch project publishes all of the opensearch modules and Opensearch-project-provided plugins to maven central.
This allows some users of opensearch to embed opensearch in their own JVM applications, loading plugins directly via custom dependency management and build tools e.g. maven, sbt, gradle, leiningen, ...; and injecting the plugin classes directly into OpenSearch Node instances.
would it be feasible to publish this plugin as an artifact to the io.aiven org on mvnrepository?
This would allow us a internally "compliant" way to take this to production.
The text was updated successfully, but these errors were encountered: