-
Notifications
You must be signed in to change notification settings - Fork 37
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 releases to maven #64
Comments
Hi @rursprung If I read it correctly you would like to have the Do I get correctly? |
not quite: the idea would be that the publish would happen as part of your normal release, so that it's on maven central (or any other public maven repo). then it can be pulled in by everyone who needs it (or manually downloaded; same as through the GH releases page - that way it can act as a mirror as well). |
I was looking at this and I ran into some issues, see opensearch-project/OpenSearch#3649 I will keep the ticket open but for the time being the status is: |
@lukas-vlcek you could remove url & scm section from |
I think this is also related: opensearch-project/OpenSearch#3692 |
@rursprung based on the discussion in opensearch-project/OpenSearch#3692 I will "friendly" close this ticket as won't fix. Once OpenSearch enables custom groupId values in POM we can revisit it. |
Status update:
|
Update:
Once the OpenSearch release 2.4 is out we can re-open this ticket. |
@lukas-vlcek 2.4 is out, i guess this can be re-opened? (not something that i can do) 🙂 |
Sure, we can now continue. I think one of the changes I would like to do first is changing the "package" name of internal classes to something that will match the groupId in the maven repo. Perhaps to something like (Although it is possible to override the |
@lukas-vlcek: do you think it'd now be possible to pick this up? the packages are still named |
Hello, any plans for this to be worked on in the near future? |
Right, I will start working on that too. It will need to become part of the release process. The following are some articles to start with: |
it'd be great if you could publish your releases to maven (we use it to manage our dependencies, incl. opensearch & opensearch plugins).
you can use the
opensearch.pluginzip
gradle plugin for this: see the opensearch plugins documentation on this and opensearch-project/opensearch-build#1916.The text was updated successfully, but these errors were encountered: