Eclipse gradle and maven tooling - local resolution -


i want gradually migrate multi-module maven build multi-module gradle build.

i'm using m2e maven tooling in eclipse , 1 feature if projecta depends on projectb , both projects in eclipse workspace, m2e smart enough use local .class files projectb instead of using .jar file maven repository. let's call feature "local resolution".

so, can eclipse gradle tooling , m2e play nicely together?

  1. if gradle project depends on maven project, can maven project locally resolved
  2. if maven project depends on gradle project, can gradle project locally resolved
  3. if gradle project depends on gradle project, can dependent gradle project locally resolved?

resolving local gradle projects blocked until gradle-2750 resolved. current state this:

  1. local resolution works gradle project depending on maven project (fixed in version 3.1.0.m1)
  2. local resolution fails maven project depending on gradle project
  3. local resolution fails gradle project depending on gradle project

related sts issues

update

gradle-2750 has been fixed , available in next gradle release, gradle 1.12.


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -