Classpath order when generating project files with Eclipse plugin
I have a multi-project build with two subprojects "a" and "b". "b" depends on "a". Both subprojects declare Guava as first level dependency. "a" uses version 15.0 whereas "b" uses 16.0.1.
Running gradle b:dependencies demonstrates that the latest version is picked. However, when generating the Eclipse project files with the Gradle Eclipse plugin (by executing gradle eclipse) version 15.0 is found first on the classpath as we have a project dependency on "a". It looks like depending on another project reference also adds all external dependencies but without any conflict resolution. They are resolved first on the classpath.