Hi, I'm looking to develop a gradle plugin to support the new Sonatype Central Publishing Portal workflow, as new Central Portal does not support uploading via the maven plugin (bruh), Basically what I want to do is, I want to create my own type of

ArtifactRepository

, similar to a

MavenArtifactRepository

, however it • only accepts uploads (not downloads) of artifacts • will pack all the artifacts into a zip before uploading • otherwise acts identically to

DefaultMavenArtifactRepository

(ie. will generate

.sha1

,

.sha256

, and

.sha512

files,

.md5

files, will build the pom, etc.) the problem is, looking at how

ArtifactRepository

are implemented, it seems like I'd need to use a lot of internal apis, as I'd most likely need to have my own instance of

MavenPublisher

, among other things, in order to be able to properly bundle the files into a zip. does anyone happen to know of any custom implementations of `ArtifactRepository`s I could look at, or some pointers on what things I should look into?

Thank you for your interest in Gradle!

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

from: the issue you linked

not easily as far as I know

doing that would be possible, but it is jank and not the solution I'd like

why is it jank? can all be done from within Gradle

because you're not explicitly using task dependencies instead you're implicitly relying on how gradle structures the resulting published artifacts I'd much prefer if I could somehow have my own maven publisher is there really no way to be able to inherit from

AbstractMavenPublisher

?