:white_check_mark: RESOLVED : see the thread insid...

# compose-desktop

[wiktor]

✅ RESOLVED : see the thread inside (TLDR; remove ~/.gradle catalog)
hey 👋 I wonder if anybody has a problem with running desktop todo app from examples? Android and iOS works fine but for desktop I get (on mac):

* What went wrong:
Could not determine the dependencies of task ':desktop:compileJava'.
> Could not resolve all dependencies for configuration ':desktop:compileClasspath'.
   > A problem occurred configuring project ':common:utils'.
      > org.gradle.api.internal.initialization.DefaultClassLoaderScope@2bfecddc must be locked before it can be used to compute a classpath!

[wiktor]

I tried to delete gradle cache, different gradle and kotlin versions, but without luck, other sample (codeviewer) works without any issues

[wiktor]

Staktrace

* Exception is:
org.gradle.api.internal.tasks.TaskDependencyResolveException: Could not determine the dependencies of task ':desktop:compileJava'.
        at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.getDependencies(CachingTaskDependencyResolveContext.java:71)
        at org.gradle.execution.plan.TaskDependencyResolver.resolveDependenciesFor(TaskDependencyResolver.java:46)
        at org.gradle.execution.plan.LocalTaskNode.getDependencies(LocalTaskNode.java:155)
        at org.gradle.execution.plan.LocalTaskNode.resolveDependencies(LocalTaskNode.java:123)
        at org.gradle.execution.plan.DefaultExecutionPlan.doAddNodes(DefaultExecutionPlan.java:171)
        at org.gradle.execution.plan.DefaultExecutionPlan.addEntryTasks(DefaultExecutionPlan.java:135)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.addEntryTasks(DefaultTaskExecutionGraph.java:160)
        at org.gradle.execution.TaskNameResolvingBuildConfigurationAction.configure(TaskNameResolvingBuildConfigurationAction.java:49)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:55)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:26)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:63)
        at org.gradle.execution.DefaultTasksBuildExecutionAction.configure(DefaultTasksBuildExecutionAction.java:45)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:55)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:26)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:63)
        at org.gradle.execution.ExcludedTaskFilteringBuildConfiguratio

[jim]

I have no troubles running the todo app sample using ./gradlew :desktop:run --no-daemon on the latest commit (21146ed1d5174a9a1b2dad6e1376d4bd9c764b7e), so it appears the issue is on your end.

[jim]

Given the nature of your error message, it might be a gradle issue. Gradle is notoriously buggy. When I run into such issues, I typically do the following:
1. delete my ~/.gradle/ directory with rm -rf ~/.gradle/
2. use jps -m to find anything with the word "Daemon" in it, especially gradle daemons, and kill them using kill -9 [pid]
3. do a ./gradlew clean --no-daemon

[jim]

If that still doesn't work, I'd be curious to see the output of ./gradlew --version --no-daemon on your machine.

[eygraber]

I usually just run gradle (or ./gradlew) --stop

It seems like if you update while a daemon is running it can run into some issues. Something about not isolating classpaths IIRC

[wiktor]

guys thank you for the help, @jim’s steps solved the problem! I tried --stop and removing ~/.gradle/cache before asking for a help - so it turns out removing whole folder does the trick

[jim]

Yeah, deleting gradle usually helps improve everything 😛🤣