When using Maven, if I load a dependency as a project in Eclipse, it start automatically to use the loaded project, so that if I modify the dependency code in Eclipse the changes will apply immediately, it will even apply the code change to the runtime if my application/server was already started, in other words, Hotswap is also working.
But with Gradle, it seems we are stuck to have all dependencies been part of a giant Gradle multi-projects, which is unlikely feasible in most normal business application having a minimum of complexity. Think about it, it’s unlikely that you are the owners of all dependencies that your project is using.
I found a plug-in that try to resolve some of the issue but it doesn’t really work, and it also show warning that Gradle 2 doesn’t like some of its construct. The plug-in is called gradle-eclipselinkprojects, downloadable at -> https://projects.emesit.de/projects/gradle-eclipselinkprojects/wiki.
That issue is the worst I know about Gradle. It’s hard to justify using Gradle when we are used to seamless integration when using Maven.
Any plan to fill the gap with Maven and provide usable support for more than one projects in Eclipse?