Geek Answers Handbook

Eclipse gradle workspace resolution between gradle broken projects

2 gradle projects, A and B, where A compiles a dependency on B. Remappig JARs are allowed for maven and gradle projects. I tried with the enabled and disabled custom tool model. I have local repositories defined in a file in the init.d directory.

Question 1: Why am I getting an underdeveloped dependency error for project B when resolving dependencies for A? Despite the fact that B is not deployed in any of the repositories, the resolution of the workspace should begin and allow it the same way as for maven projects (this works btw).

Question 2: Should B have anything special except the group and version defined in the build.gradle file for visibility to resolve the workspace?

I am running eclipse 4.4.1 and gradle IDE 3.7.0.201503301651-CI-B39. I also tried a stable version with the same eclipse version.

When I start with --debug, I see how gradle is trying to resolve local repositories and not refuse?

+4
source share
1 answer

The answer to your question comes down to the fact that there is no workspace permission, as you might know from maven / m2e.

"reassigning" dependencies does not "allow" projects in the workspace in the sense that it considers the workspace as a kind of repository.

Gradle , . , jar- . "" ( "" ) jar .

, , , , - , , . ( , "" )

, ...

+5

More articles:


All Articles