On 01/26/2016 09:20 PM, Lars Vogel
wrote:
The different classpath scopes in Android Gradle
(main/test/androidTest) may be a challenge I think the only
practical solution is to put all of the dependencies into the JDT
classpath.
That's one of the topics I'm regularly brainstorming about. And I
believe this can be supported "enough" without changing JDT. Here
are a couple of proposals for m2e, that I believe can be a way
forward a better handling of "classpath scopes" in Java projects:
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=486035
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=486032
I would highly welcome some other opinions about those 2 proposals,
and whether those apply to BuildShip as well. But it actually seems
to me that just adding the "scope" logic to m2e or BuildShip might
even be a better solution than tweaking JDT. Then, if some
factorization seem possible (such as metadata to store source
folder<->scope<->classpath container) then we can
probably come with a proposal for JDT.
|