Gustav Tross
05/17/2024, 12:27 PMapi(projects.a.domain)
a:domain doesn’t have any dependencies
When I try to build my project I get this exception:
FAILURE: Build failed with an exception.
* What went wrong:
Circular dependency between the following tasks:
:b:domain:allMetadataJar
+--- :b:domain:compileCommonMainKotlinMetadata
| +--- :b:domain:allMetadataJar (*)
| \--- :b:domain:transformCommonMainDependenciesMetadata
| +--- :b:domain:allMetadataJar (*)
| +--- :b:domain:iosArm64MetadataJar
| | +--- :b:domain:compileAppleMainKotlinMetadata
| | | +--- :b:domain:allMetadataJar (*)
| | | +--- :b:domain:compileCommonMainKotlinMetadata (*)
| | | +--- :b:domain:compileNativeMainKotlinMetadata
| | | | +--- :b:domain:allMetadataJar (*)
| | | | +--- :b:domain:compileCommonMainKotlinMetadata (*)
| | | | +--- :b:domain:metadataCommonMainClasses
| | | | | \--- :b:domain:compileCommonMainKotlinMetadata (*)
| | | | \--- :b:domain:transformNativeMainDependenciesMetadata
| | | | +--- :b:domain:allMetadataJar (*)
| | | | +--- :b:domain:iosArm64MetadataJar (*)
| | | | +--- :b:domain:iosSimulatorArm64MetadataJar
| | | | | +--- :b:domain:compileAppleMainKotlinMetadata (*)
| | | | | +--- :b:domain:compileIosMainKotlinMetadata
| | | | | | +--- :b:domain:allMetadataJar (*)
| | | | | | +--- :b:domain:compileAppleMainKotlinMetadata (*)
| | | | | | +--- :b:domain:compileCommonMainKotlinMetadata (*)
| | | | | | +--- :b:domain:compileNativeMainKotlinMetadata (*)
| | | | | | +--- :b:domain:metadataAppleMainClasses
| | | | | | | \--- :b:domain:compileAppleMainKotlinMetadata (*)
| | | | | | +--- :b:domain:metadataCommonMainClasses (*)
| | | | | | +--- :b:domain:metadataNativeMainClasses
| | | | | | | \--- :b:domain:compileNativeMainKotlinMetadata (*)
| | | | | | \--- :b:domain:transformIosMainDependenciesMetadata
| | | | | | +--- :b:domain:allMetadataJar (*)
| | | | | | +--- :b:domain:iosArm64MetadataJar (*)
| | | | | | +--- :b:domain:iosSimulatorArm64MetadataJar (*)
| | | | | | +--- :b:domain:iosX64MetadataJar
| | | | | | | +--- :b:domain:compileAppleMainKotlinMetadata (*)
| | | | | | | +--- :b:domain:compileIosMainKotlinMetadata (*)
| | | | | | | +--- :b:domain:compileNativeMainKotlinMetadata (*)
| | | | | | | +--- :b:domain:metadataAppleMainClasses (*)
| | | | | | | +--- :b:domain:metadataIosMainClasses
| | | | | | | | \--- :b:domain:compileIosMainKotlinMetadata (*)
| | | | | | | \--- :b:domain:metadataNativeMainClasses (*)
| | | | | | +--- :b:domain:transformAppleMainDependenciesMetadata
| | | | | | | +--- :b:domain:allMetadataJar (*)
| | | | | | | +--- :b:domain:iosArm64MetadataJar (*)
| | | | | | | +--- :b:domain:iosSimulatorArm64MetadataJar (*)
| | | | | | | +--- :b:domain:iosX64MetadataJar (*)
| | | | | | | +--- :b:domain:transformCommonMainDependenciesMetadata (*)
| | | | | | | \--- :b:domain:transformNativeMainDependenciesMetadata (*)
| | | | | | +--- :b:domain:transformCommonMainDependenciesMetadata (*)
| | | | | | \--- :b:domain:transformNativeMainDependenciesMetadata (*)
| | | | | +--- :b:domain:compileNativeMainKotlinMetadata (*)
| | | | | +--- :b:domain:metadataAppleMainClasses (*)
| | | | | +--- :b:domain:metadataIosMainClasses (*)
| | | | | \--- :b:domain:metadataNativeMainClasses (*)
| | | | +--- :b:domain:iosX64MetadataJar (*)
| | | | \--- :b:domain:transformCommonMainDependenciesMetadata (*)
| | | +--- :b:domain:metadataCommonMainClasses (*)
| | | +--- :b:domain:metadataNativeMainClasses (*)
| | | \--- :b:domain:transformAppleMainDependenciesMetadata (*)
| | +--- :b:domain:compileIosMainKotlinMetadata (*)
| | +--- :b:domain:compileNativeMainKotlinMetadata (*)
| | +--- :b:domain:metadataAppleMainClasses (*)
| | +--- :b:domain:metadataIosMainClasses (*)
| | \--- :b:domain:metadataNativeMainClasses (*)
| +--- :b:domain:iosSimulatorArm64MetadataJar (*)
| \--- :b:domain:iosX64MetadataJar (*)
\--- :b:domain:metadataCommonMainClasses (*)
changing the name to of b:domain to b:foobar fixes the issue. It seems very similar to this https://youtrack.jetbrains.com/issue/KT-30348 but that was fixed a long time ago. Anyone got any tips on how to fix this without having to come up with unique project names for all module?Adam S
05/17/2024, 1:09 PMgroup
to be different in each subproject. That way the Maven group:artifact
coordinates will be distinct per subproject, so Gradle can differentiate them.Gustav Tross
05/17/2024, 2:18 PM