-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Maintain a NuGet package #27067
Comments
We are not going to do this as this is not a common way of distributing Java-based software. |
Thanks for the quick response! |
One note: it’s “Elasticsearch”, not “ElasticSearch”. 😀 |
@HarelM We are working on extracting the framework that we have as part of the .NET client for running integration tests against Elasticsearch. This framework can download Elasticsearch zip archives and run them. See elastic/elasticsearch-net#2767 |
This looks promising, but is 5 month old. :-/ |
@HarelM let's have the discussion on the other issue please. |
@russcam Sure, no problem, posted there my thoughts and current work. |
Describe the feature
Maintain a NuGet package.
Justification:
I'm using ES as part of my open source project.
The setup of this project requires the presence of ES.
In order for the setup instruction to be simpler I decided to store the binaries of ES as part of my repository (which is a bad practice) - I'm doing this since I write in C# and can't use java package managers such as Maven.
I'm planning on migrating all my 3rd party packages to NuGet but I prefer that the owners of the packages will maintain the NuGet package instead of me...
Any thoughts are welcome.
The text was updated successfully, but these errors were encountered: