Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

756
Visualizações
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 Respostas
Responde à pergunta

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 Relatório

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 Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda