Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

754
Views
Eclipse: reference local code instead of cached gradle dependency

I have two gradle java projects imported into Eclipse, one being a dependency of the other. I would like for Eclipse to use the local dependency code, instead of the compiled dependency in the gradle cache folders, so I can modify and debug both projects simultaneously.

How do I force Eclipse to use a local dependency code?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

The feature you are referring to is known as Composite Builds:

Importing into the IDE

One of the most useful features of composite builds is IDE integration. By applying the idea or eclipse plugin to your build, it is possible to generate a single IDEA or Eclipse project that permits all builds in the composite to be developed together.

In addition to these Gradle plugins, recent versions of IntelliJ IDEA and Eclipse Buildship support direct import of a composite build.

Importing a composite build permits sources from separate Gradle builds to be easily developed together. For every included build, each sub-project is included as an IDEA Module or Eclipse Project. Source dependencies are configured, providing cross-build navigation and refactoring.

The most simple way of achieving this is to use includeBuild in your settings.gradle.

rootProject.name = 'my-composite'

includeBuild 'my-app'
includeBuild 'my-utils'

With that in place, there's no need to configure the build path manually in Eclipse.

over 4 years ago · Santiago Trujillo Report

0

Gosh this was a trivial one and it took me way too long to figure it out.

Solved the issue by creating a file named external-projects.properties in the root folder of the parent project with the relative or full path to the dependency project folder.

To be precise, for me the folders tree ends up like this:

git-folder/
|__parent-project/
   |__external-projects.properties
   |__build.gradle.kts
   |__rest (src/main, etc)
|__dependency-project/
   |__build.gradle.kts
   |__rest (src/main, etc)

And the contents of the external-projects.properties file:

dependency-project = ../dependency-project

The dependency project must also be in the build path of the parent project (done by "Right-Click project > Build Path > Configure Build Path" and adding it in the "Projects" tab).

After that, a "Right Click > Gradle > Refresh Gradle Project" did the trick.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!