All geek questions in one place

Eclipse gradle and maven tooling - local resolution

I want to gradually migrate the multi-module maven assembly to the multi-module gradle construct.

I am currently using m2e maven tooling in eclipse, and I like that if projectA is dependent on projectB and both projects in my eclipse workspace, m2e is smart enough to use local .class files for projectB instead of using the .jar file from my maven repository. Let me call this feature "local resolution".

So, can the eclipse gradle and m2e tool play beautifully together?

  • If the gradle project depends on the maven project, is it possible to locally resolve the maven project.
  • If the maven project depends on the gradle project, can the gradle project be locally resolved
  • If the gradle project depends on the gradle project, is it possible to locally resolve the dependent gradle project?
+3
source share
2 answers

Allowing local gradle projects is blocked until GRADLE-2750 is resolved. So the current state:

  • Local resolution works for the gradle project depending on the maven project (fixed in version 3.1.0.M1)
  • Local permission doesn't work for maven project depending on gradle project
  • Local permission not executed for gradle project depending on gradle project

STS related issues

Update

GRADLE-2750 is fixed and will be available in the next version of gradle, gradle 1.12.

+4
source

The upcoming support for composite builds in the buildship plugin sounds very promising.

From what I see, this will solve question 3.

0
source

Source: https://habr.com/ru/post/976540/

More articles:


All Articles