For Eclipse class path, which points to .../.gradle/cache/..., you could replace the part before /.gradle/cache with USER_HOME and create a classpath extending the variable USER_HOME. Each user just has to set this variable once and all projects will be ok.

For IntelliJ I didn't find a feature similar to Eclipse classpath variables.

Probably this is the way to go (like the Maven Eclipse plugin works).

IntelliJ has some concept for this. I haven't fully figured it out yet. Unfortunately we don't have any IntelliJ file generation yet.

>>For Eclipse class path, which points to .../.gradle/cache/..., you could replace the part before /.gradle/cache with
>>USER_HOME and create a classpath extending the variable USER_HOME. Each user just has to set this variable
>>once and all projects will be ok.

i think it would be better to use Classpath-Variable GRADLE_REPO
like maven uses M2_REPO.

as Classpath-Variables are bound to eclipse-workspace and workspaces
are 'per user', switching users should not be a problem.

We also have the use case that there are resolvers which don't use the cache for the jars. Like the resolver you get with addFlatDirResolver. Usually in such a case the libs live in svn and are relative to the project root. We also need to offer to use classpath variables in such a scenario.