Martmists
11/30/2025, 6:20 PMval outputJar by configurations.creating {
isCanBeConsumed = false
}
dependencies {
outputJar(project(":mmorpg-mod", outputJar.name))
}
tasks {
val deploy by registering(SshDeployTask::class) {
host = prop("sshDeployHost")
port = prop("sshDeployPort").toInt()
user = prop("sshDeployUser")
if (localProps.hasProperty("sshDeployPass")) {
password = prop("sshDeployPass")
}
remoteDir = prop("sshDeployPath")
from(outputJar)
}
}
mmorpg-mod subproject:
val outputJar by configurations.creating {
isCanBeResolved = true
isCanBeConsumed = true
}
artifacts {
add(outputJar.name, tasks.named("remapJar"))
}
Error:
Could not determine the dependencies of task ':deploy'.
> Could not resolve all dependencies for configuration ':outputJar'.
> Could not resolve project :mmorpg-mod.
Required by:
root project 'mmorpg-mod'
> A dependency was declared on configuration ':mmorpg-mod:outputJar' of 'root project :' but no variant with that configuration name exists.TheGoesen
12/01/2025, 10:15 AMRequired by:
root project 'mmorpg-mod'
So your root project name is "morpg-mod" (check your settings.gradle.kts) and your subproject name is also "mmprg-mod".
I would advise to always use unique names. One of the longest standing and most commented bug of gradle ist that dependency resolution gets terrible confused when project names are not uniqueMartmists
12/01/2025, 10:18 AM