Generated task names are strange in Kotlin Multiplatform project

[StefMa]

Description

Given I have a KMP project with multiple targets, running ./gradlew tasks reveals:

This doesn't make any sense I guess 🤔

Why should I publish all publications to a specific nmcpJvmRepository?

Something like this publishJvmPublicationToNmcpMingwX64Repository also exists, respectively for all targets.

I would expect we only have something like this
publish{target}PublicationToNmcp{target}Repository

[martinbonnin]

This is a side effect of using maven-publish and creating one repo per publication to avoid overlapping output directories (see #34).

Long term, I'd like to remove the dependency on maven-publish to avoid those issues, I have created #81 as a follow up.

[vlsi]

WDYT of hiding the generated technical tasks by configuring group=null so the users do not get clutter in gradlew tasks output?

[martinbonnin]

WDYT of hiding the generated technical tasks by configuring group=null so the users do not get clutter in gradlew tasks output?

Do you mean mutate the maven-publish tasks like publishFooPublicationToBarRepository by removing their group?

That's an idea but I find it always a bit dangerous to modify the state of other plugins in general. It could be suprising if someone wanted to still use the "old" and "new" publishing tasks...

I'm currently reshuffling things to not rely on those publishFooPublicationToBarRepository tasks. Hoping to get something out this week, will keep this issue updated.

[vlsi]

Do you mean mutate the maven-publish tasks like publishFooPublicationToBarRepository by removing their group?

Exactly.

That's an idea but I find it always a bit dangerous to modify the state of other plugins in general. It could be suprising if someone wanted to still use the "old" and "new" publishing tasks...

Frankly, you create technical repository which no-one uses, and no-one should use except nmcp, then you use the task expliciltly:

nmcp/src/main/kotlin/nmcp/NmcpExtension.kt

Lines 45 to 47 in eb08cc3

	val publishToNmcpTaskProvider = project.tasks.named("publish${capitalized}PublicationTo${repoName.capitalized()}Repository")
	publishToNmcpTaskProvider.configure {

There's nothing wrong hiding the task so users get better developer experience.

I'm currently reshuffling things to not rely on those publishFooPublicationToBarRepository tasks

Frankly, I would rather like hiding the tasks now and get a release that do not require publish... tasks in a couple of months than wait for weeks for getting exactly the same user experience.
You do configure the task already, and the only missing bit is group = null // Hide the task from gradlew tasks output for better user experience. That single line of code plus a release would make a difference.

The thing is that extra tasks do not bother me as a end-user (they do bother me as Gradle plugin developer though), however, having a better dev-ex is better than having cleaner code.

By the way, I've filed the same issue against Gradle long-time ago: gradle/gradle#10132.

[martinbonnin]

Frankly, you create technical repository which no-one uses, and no-one should use except nmcp, then you use the task

Right, the repos are internal so it makes sense to hide the tasks.

Frankly, I would rather like hiding the tasks now and get a release that do not require publish... tasks in a couple of months than wait for weeks for getting exactly the same user experience.

That's fair. Give me until end of this week so hopefully we don't have to wair for months 🤞

[martinbonnin]

The publishing tasks are now hidden in #95 and there should be a lot less task because only a single repository is now configured per-project (see #111).

The hidden tasks will probably stay around for the foreseeable future (see also #81 (comment))