I need to redistribute gradle generated Eclipse .classpath files for convenient use by other develoeprs in our department. Now I experienced a problem with changing modules, i.e. modules that keep their name but underly ongoing changes. Unfortunately the generated .classpath makes direct use of the local gradle chache, which uses some kind of SHA keys to distinguish certain versions of the same artifact (name). Thus the generated .classpath files are always out-dated if one of the dependency changing modules changes.
Is there a way to introdcue some kind of indirection, e.g. mirror the cache to a stable structure and let the .classpath entries point to this structure?