Lukáš Vlček

Thanks @smbambling for putting the effort into write it all down.

Hi @rursprung If I read it correctly you would like to have the `apply plugin: 'opensearch.pluginzip'` be added to `build.gradle` so that you can call the new custom publish task...

I was looking at this and I ran into some issues, see https://github.com/opensearch-project/OpenSearch/issues/3649 It seems the bug will be fixed soon (kudos to @reta) but we will be able to...

I think this is also related: https://github.com/opensearch-project/OpenSearch/issues/3692

@rursprung based on the discussion in https://github.com/opensearch-project/OpenSearch/issues/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: - A blog post about the ZIP pom publication plugin has been published: https://opensearch.org/blog/technical-post/2022/08/opensearch-plugin-zips-now-in-maven-repo/ - A PR to allow maven pom `groupId` customization is being reviewed: https://github.com/opensearch-project/OpenSearch/pull/4156

Update: - The Zip publication POM `groupId` customization will be available starting with OpenSearch release v2.4: https://github.com/opensearch-project/opensearch-build/issues/2521 Once the [OpenSearch release 2.4](https://github.com/opensearch-project/opensearch-build/issues/2649) is out we can re-open this ticket.

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...

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: - [Publishing Java packages...

Good idea. Right now the migration should be simple (except the prefix as you pointed out).