This message was deleted.

They are not generated in the same directory, not more than all tasks have their output in the same

build

directory. Each of the publications has its own output directory. I'd expect the tasks to run in parallel with CC.

if I’m using a file-based repo then they’ll all end up in the same directory some how, I’m pretty sure it’s the

PublishToMavenRepository

tasks that are doing that

publishing {
  repositories {
    maven(file("build/custom-maven-repo")) {
      name = "LocalDir"
    }
  }
}

Again, each task has its dedicated directory underneath. Just like all tasks have their output in

build

sorry, I don’t understand what you mean. I only see one directory…

ooh you mean nested within the

build/custom-maven-repo

directory

Exactly, the output directories for the actual tasks are

build/custom-maven-repo/foo/foo.gradle.plugin

,

build/custom-maven-repo/foo/bar.gradle.plugin

, and

build/custom-maven-repo/com/example/mycode/

.

but what happens if the publications have outputs that might overlap? (Which Gradle will print warnings about). Will Gradle detect this and decide the tasks won’t run in parallel?

I don't know, but I also don't know what you mean. How could there be an overlap? Every artifact has its own publish task. Only problem I could imagine is if you have different artifacts with the same coordinates, but that would mean your build simply is misconfigured.

How could there be an overlap?

yeah, through misconfiguration

Well, then just fix the misconfiguration. 😄 I'm not sure how it would behave, just try it and see. 🙂

yeah for sure, I can fix bad config like that, but I was using that as an example. I was curious if Gradle determined parallelism based on task output.

Afaik if CC is in use, all tasks are run in parallel, unless one depends on the other