This message was deleted.

I guess https://github.com/gradle/gradle/issues/847 is somewhat related.

You can change the names of the JARs using

archivesBaseName

(https://docs.gradle.org/current/dsl/org.gradle.api.Project.html#org.gradle.api.Project:archivesBaseName) or

base.archivesName

(https://docs.gradle.org/current/dsl/org.gradle.api.plugins.BasePluginExtension.html#org.gradle.api.plugins.BasePluginExtension:archivesName) in the projects.

Thanks, I'll check that.

I would always define names in the settings file (although the API is not that elegant yet). It's the way of least confusion. And the way that fits the idea of a clear component identity in Gradle's model when it comes to dependency management. You then have a uniques simple name for each project, that is used for the Jar names and would also be used in the coordinates if you should publish the project or address it from another build in a composite build context. You could 'automate' the name assigning (e.g. always put the parent folder name as prefix) in the settings file by looping through your folders and doing the "include" and "projectDir" based on the project path. (Maybe someday this will be followed up on https://github.com/gradle/gradle/issues/14561 and a cleaner API for the settings file emerges)

Thanks @Jendrik Johannes for your input!