Latest Articles
Aug 4

svn: The repository at ‘‘ has uuid ‘‘, but the WC has ‘

If you’ve ever tried to switch your current working copy to a new SVN URL with ‘svn switch –relocate [old_repo] [new_repo]‘ command you may run into an error message similar to this:

svn: The repository at ‘[new_repo]‘ has uuid ‘[new_uuid]‘, but the WC has ‘[old_uuid]‘

The reason for this is that Subversion expects the same repository from the svn switch command and you wouldn’t run into this problem if you had done an svnsync on it.

At any rate, to solve the above error, you must do an svnadmin setuuid [path/to/new/repo] ‘[old_uuid]‘ on your new repo so that the uuid matches. Hope that solves your problem.

Jul 13

Could not find com.google.gwt.dev.Compiler. Make sure you have it in your classpath

If you ever run into an exception similar to the following:

Execution failed for task ‘:common:gwt-utils:gwtCompile’.
at org.gradle.api.internal.tasks.DefaultTaskExecuter.executeActions(DefaultTaskExecuter.java:66)
at org.gradle.api.internal.tasks.DefaultTaskExecuter.execute(DefaultTaskExecuter.java:43)
at org.gradle.api.internal.project.taskfactory.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:32)
at org.gradle.api.internal.project.taskfactory.ExecutionShortCircuitTaskExecuter.execute(ExecutionShortCircuitTaskExecuter.java:50)
at org.gradle.api.internal.tasks.SkipTaskExecuter.doExecute(SkipTaskExecuter.java:57)
at org.gradle.api.internal.tasks.SkipTaskExecuter.execute(SkipTaskExecuter.java:35)
at org.gradle.api.internal.tasks.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:32)
at org.gradle.api.internal.AbstractTask.execute(AbstractTask.java:231)
at org.gradle.execution.DefaultTaskGraphExecuter.executeTask(DefaultTaskGraphExecuter.java:167)
at org.gradle.execution.DefaultTaskGraphExecuter.doExecute(DefaultTaskGraphExecuter.java:160)
at org.gradle.execution.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:78)
at org.gradle.execution.TaskNameResolvingBuildExecuter.execute(TaskNameResolvingBuildExecuter.java:113)
at org.gradle.execution.DelegatingBuildExecuter.execute(DelegatingBuildExecuter.java:54)
at org.gradle.execution.DelegatingBuildExecuter.execute(DelegatingBuildExecuter.java:54)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:153)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:107)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:75)
at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:41)
at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:27)
at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:209)
at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:193)
at org.gradle.launcher.Main.execute(Main.java:55)
at org.gradle.launcher.Main.main(Main.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:46)
at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:28)
at org.gradle.launcher.GradleMain.main(GradleMain.java:24)
Caused by: : Java returned: 1

-or-

Could not find com.google.gwt.dev.Compiler. Make sure you have it in your classpath

..and you’ve explored all options/fixes with no luck, perhaps you may be overlooking one elementary item. Is the project you’re trying to compile sitting in a directory path with spaces? If so, that’s your problem. It’s the age old Unix dislike for spaces in directory.

Sep 17

svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists

Ever gotten this Subversion checkout/update operation error message?

svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists

You can fix this problem by applying an extra option of “–force” to the SVN’s checkout/update command.  This will mark the folder in question as updated and the subfolder files as versioned but will not overwrite any of YOUR files in there.