Allow zip aggregation to include maven-metadata.xml files

[mmoayyed]

What feature do you want to see added?

If I run ./gradlew nmcpZipAggregation and examine the zip file generated, I do not see the maven-metadata.xml file for the artifacts. This is required for Gradle of course to locate the right artifact, particularly for snapshots, etc.

Main use case/experiment is, I'd like to unzip and upload the files to my own repository and have Gradle consume those. I can do the upload fine, but Gradle needs the xml files as well to proceed.

PS I tagged this as a Feature Request, because I am not sure if this was intentional.

Upstream changes

This might be related/relevant, though it's more about the actual task of publishing artifacts:
#73

Are you interested in contributing this feature?

Sure, with a bit of help. I am not all too familiar with Kotlin, but happy to take a pass.

[martinbonnin]

This is on purpose because the Maven Central publishing API doesn't allow sending maven-metadata.xml files. Those files are "stateful". When you upload a release, the server looks at the current maven-metadata.xml file and "merges" the new release in.

You have nmcpPublishAggregationToMavenLocal that will publish your repository to ~/.m2. I'll look into adding custom repositories support so that you can publish to other places as well.

[mmoayyed]

Thank you very much for the answer.

Perhaps a reasonable alternative would be to allow nmcpPublishAggregationToMavenLocal to publish to a defined directory and otherwise use the local m2 directory. I don't suppose there is any way to control what MavenLocal actually is with that task, through configuration or environment variables, etc.

[martinbonnin]

I don't suppose there is any way to control what MavenLocal actually is with that task, through configuration or environment variables, etc.

There isn't right now but this is what I meant by adding custom repositories.