Hey everyone, When using Groovy and applying the `maven-publish` plugin and listing the tasks we ha...

# gradle

[FunkyMuse]

Hey everyone,

When using Groovy and applying the maven-publish plugin and listing the tasks we have the task publishAllPublicationsToMavenRepository

But when using the same maven-publish with Kotlin Gradle script, there's no task

publishAllPublicationsToMavenRepository

How do we fix this?

[Vampire]

There should be no difference between Groovy and Kotlin DSL.
Maybe you did not define any publication in the Kotlin version, or you did not define the publication repository called maven in the Kotlin version.

[FunkyMuse]

Previous setup in groovy was this

[FunkyMuse]

Screenshot_20230703-144244.png,Screenshot_20230703-144235.png,Screenshot_20230703-144229.png,Screenshot_20230703-144222.png,Screenshot_20230703-144215.png,Screenshot_20230703-144206.png

[FunkyMuse]

When translated into Kotlin

[FunkyMuse]

Screenshot_20230703-144409.png,Screenshot_20230703-144342.png,Screenshot_20230703-144336.png,Screenshot_20230703-144323.png

[FunkyMuse]

srcDirs is unable to be obtained since it's a function for Kotlin

And also sourcesets main Kotlin doesn't exist, i tried making it sourcesets["main"].allSources

[FunkyMuse]

And removed the kotlin srcDirs in order to compile because kotlin.srcDirs is a function invocation to set the srcDirs, there isn't any getter

[FunkyMuse]

Also registering the artifacts in Kotlin (last image that has the androidSourcesJar task by doing:

artifacts {     
add("archives", androidSourcesJar) 
}

[Vampire]

There are many bad-practices in that code, but the problem is exactly what I said. You did not define an repositories for publishing.

[Vampire]

While doing the transition, you moved the publishing repository to dependencyResolutionManagement { repositories { ... } } which as the name suggests is for dependency resolution, not for publishing.

[Vampire]

In the Groovy version, you had them in the publishing { repositories { ... } } where you have to define repositories for publishing.

[Vampire]

So, no publishing repository => no publishing tasks

[FunkyMuse]

I've tried but the task we use is still not available, all other tasks are (publish, publishToMavenLocal, publishReleasePublicationToMavenLocal)

But no:
publishAllPublicationsToMavenRepository

Since you mentioned bad practices, how do we make it better and also fix the issue?

[Vampire]

I've tried but the task we use is still not available

Then you still did not define the publishing repository

[Vampire]

I'm sorry, but I don't have time for an in-depth review, especially not of screenshots which always are a bad way to share code.

But some of them from a very cursory look:
- extra properties are almost always bad
- afterEvaluate is practically always bad except for very special cases
- manually manipulating the POM, especially as it then deviates from the Gradle Module Metadata
- subprojects { ... } / allprojects { ... } are bad
- project.plugins should not be used according to its JavaDoc
- apply(...) for applying plugins is bad
- tasks.creating instead of tasks.registering
- ...

[FunkyMuse]

Thanks so much, I'll try and change the aforementioned things, if I can't succeed I'll share code snippets