I still have issues with this: https://gradle-community.slack.com/archives/CA745PZHN/p1710814982761129 is there any way I can have a compile dependency on internal gradle apis? because the class I want to use,

AbstractMavenPublisher

, isn't accessible when using

implementation(gradleApi())

(even though other internal classes are..?) for some reason

What do you mean exactly with "isn't accessible"? What error do you get where?

I am incapable of importing the class, as my IDE will not resolve it, even though I can navigate to it in the sources

Unlikely, I'd say, it is an internal class :-)

because the issue I have is that I want to hook into the publishing to have it instead group all the artifacts together into a single zip file, before uploading it. and from what I can tell, the best way to do this would be to implement my own

MavenRepository

as well as a custom publisher for it that will create the artifacts, bundle them into a zip, and then upload that

How about instead registering a task that zips up those files and a task that uploads it?

yeah, but that would be relying on the implementation detail of how the files are generated from the task, which I'd prefer to avoid

And aren't there already plugins supporting the new system?

there are a few, but I didn't like them, so I'm looking to make my own

Why would it be depending on implementation detail?

because the plugins (or anyone in their buildscript) could change the directory structure they output their files in, no?

I did not say you should depend on files in the file system. Instead on the tasks that produce them. Always wire task outputs to task inputs

but then I'd need to depend on the file name, no? because I need a way to get the package its published to, the artifact name, etc. and since all that stuff is already in the pom, that seems the best way to get it

No, you shouldn't need file name. And artifacts I guess your task should be able to take from the publication configuration?

but the file needs to have a specific name, otherwise sonatype will reject it

So, as I said, take the information from the publication configuration and rename the file while packing the ZIP

thus, I can't rely on the file name of the jar from the

jar

task. so, I need some other way to get the module/version/classifier/extension and ensure the file has that name format. which is part of the

MavenArtifact

, as such it would be best to consume that

As you seem to intend to make your plugin public, I don't think depending on any internal class is "best" as it always could break in any patch release

yes, however there is also no good api for this other than relying on workarounds, so I'm forced to use this so, it's a separate, optional, component of the plugin that is only enabled when a user requests it, which should prevent it from breaking in cases where it isn't used

Why do you need to implement your own

MavenPublication

. Can't you just process a configured

MavenPublication

? And if not, there is probably also no problem to even make an own

Publication

subclass that users could then configure. Or if you need all from

MavenPublication

plus some more, maybe a

MavenPublication

subclass.

because there is no way to tell a maven publication to "not upload files and then just give them to me so I can deal with them", so I need my own one

because there is no way to tell a maven publication to "not upload files and then just give them to me so I can deal with them", so I need my own one

It's task that do it, so you could either replace the actions of those tasks by using

actions.clear()

(or

taskActions.clear()

, don't remember right now) and then registering own task actions with

doLast

or just leave the task without action.

not in its public api, but the publishing plugin registers a

PublishToMavenRepository

task which uses a

MavenPublisher

, to perform the publication, so it's probably best for me to use that as well, to keep my code similar to gradle's

But you don't want to do a Maven publishing actually, you want to upload a zip to a URL. I guess you should just not try to use Maven publisher, but 🤷‍♂️

I do kind of actually want to do maven publication. but I just need to zip the file before publishing it bc the internal structure of the zip is identical to that of a maven publication