1

I have a Gradle multi-project (Java) build. The structure of my solution looks as the following:

---Root
-----Common
-----Project1
-----Project2

Common, Project1 and Project2 are sub projects of Root. Both Project1 and Project2 dependent on Common. In gradle.build of Projects 1&2 I define this dependency as:

compile project(":common")

Until today everything worked fine. I was able to build any of projects without any issues.

Today, I changed signature of one of the methods inside Common (and successfully built it).

First, when I tried to compile Project1 or Project2, I started to receive compile error "expecting to have interface with [old signature], instead have [new signature]".

It looked like Project1 & Project2 did not received an updated version of Common, despite of declared dependency.

Then, I performed "clean" task on all projects.

Starting from this moment, both Project1 and Project2 failed to build with error "cannot resolve symbols of [class from Common]".

Obviously, Project1 and Project2 are not getting correctly Common dependency. I don't know what happened... What is more weird, is that IntelliJ shows like it recognizes classes from Common (imports are not grayed, no red lines or errors of any kind). But, Gradle build fails. It fails also if I trigger it directly from command line.

I was tried to delete Gradle cache (from .gradle folder), also cleaned cached from IntelliJ. Nothing helps.

Any help will be greatly appreciated.

Illidan
  • 4,047
  • 3
  • 39
  • 49
  • try deleting the `common` repository in `~/.gradle/caches/modules-2/files-2.1`. If that doesn't work then try again by increment the minor version of the common, project1 and project2 – user51 Dec 13 '18 at 01:26
  • Do you have "Delegate IDE build/run actions to Gradle" option enabled in "File | Settings | Build, Execution, Deployment | Build Tools | Gradle | Runner"? – y.bedrov Dec 13 '18 at 10:30
  • @y.bedrov - I don't; however I triggering build directly from Gradle panel - so it is Gradle's build, not Intellij. Also, the issue happens also if I triggering build directly from command line – Illidan Dec 13 '18 at 12:42
  • @Rajkumar Natarajan: I cleared (deleted) everything from caches folder - no success. About versioning: could you please explain why versioning has any impact in inter-project dependencies? – Illidan Dec 13 '18 at 12:45
  • @lldian - I got different project in maven and someone suggested a similar solution. https://stackoverflow.com/questions/52229795/couldnt-execute-maven-multi-module-project-using-exec-maven-plugin – user51 Dec 13 '18 at 14:24
  • Please add the `settings.gradle` to your question and a minimal project `build.gradle` so applied plugins are shown. Also I would suggest trying to fix command line first, move to IDE after. – Louis Jacomet Dec 17 '18 at 09:23

0 Answers0