Ability to specify Maven publication

[Anamorphosee]

What feature do you want to see added?

One of the modules in my project contains 2 Maven publications (one for Maven Central and another for Gradle plugin portal). I currently use Nmcp version 0.0.9 and can set publication name for it.

nmcp {
    publish(mavenPublicationName) {}
}

In the new Nmcp version (0.1.5) I can't specify publication and it tries to publish both my publications.

Could you please return the ability to set publication name manually?

Upstream changes

No response

Are you interested in contributing this feature?

No response

[martinbonnin]

Good catch, this is an overshoot of #29, will fix this for the next version.

[vlsi]

@Anamorphosee , just wondering: what is wrong with publishing both publications?
Frankly speaking, I do publish both publications to both Gradle Plugin Portal and Maven Central for my Gradle plugins.

[Anamorphosee]

@vlsi Well. First of all trying to apply Nmcp version 0.1.5 leads to error:

> Task :zipAggregation FAILED

[Incubating] Problems report is available at: file:///Users/denis/sources/stacktrace-decoroutinator/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':zipAggregation'.
> Entry dev/reformator/stacktracedecoroutinator/dev.reformator.stacktracedecoroutinator.gradle.plugin/2.5.5/dev.reformator.stacktracedecoroutinator.gradle.plugin-2.5.5.pom is a duplicate but no duplicate handling strategy has been set. Please refer to https://docs.gradle.org/8.14.1/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:duplicatesStrategy for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 17s
96 actionable tasks: 50 executed, 46 up-to-date

And secondly: The plugin com.gradle.plugin-publish creates 2 artifacts to publish - marker and plugin. For Maven Central I don't want to publish marker. And moreover: for Maven Central there have to be another Artifact Name - dev.reformator.stacktracedecoroutinator.gradle.plugin, while for Gradle plugin portal artifact name is dev.reformator.stacktracedecoroutinator

[Anamorphosee]

@vlsi

Frankly speaking, I do publish both publications to both Gradle Plugin Portal and Maven Central for my Gradle plugins.

do you publish both Marker and plugin to Maven Central?

[vlsi]

do you publish both Marker and plugin to Maven Central?

Sure do I. Why would you skip publishing the markers to Central?

[martinbonnin]

@Anamorphosee same here. For some of my plugins, I also stopped publishing on the Gradle Portal because it duplicates information. See gradle/plugin-portal-requests#225

[Anamorphosee]

@Anamorphosee same here. For some of my plugins, I also stopped publishing on the Gradle Portal because it duplicates information. See gradle/plugin-portal-requests#225

Well. I still want to publish my plugin both to Maven Central and Gradle plugin portal.

[Anamorphosee]

@vlsi

Sure do I. Why would you skip publishing the markers to Central?

May I somewhere look at a working example of a project publishing Gradle plugin both to Maven Cental and Gradle plugin portal?

[vlsi]

Here's a plugin I released with nmcp recently: https://github.com/burrunan/gradle-s3-build-cache/blob/ed262cc3c0f16b7afc2396cc21d68cb7817a304a/build.gradle.kts

[Anamorphosee]

Ok. Seems my case can be solved by publishing the marker and configuring the Maven publication for Gradle plugin.

But still I think it will be useful to specify the publication, especially when this feature was presented in older versions of Nmcp. It was exactly the feature for which I preferred Nmcp over other alternatives.

[martinbonnin]

After some back and forth on this, I decided to remove the ability to publish single publications (#111). This simplifies the code a lot and in that specific instance, publishing the marker to maven central is the way to go.

If anyone else has another use case, please comment here and I'll revisit.