The attached archive migrationtest.zip contains one library and two wtp projects.
My goals was providing examples for:
gradle support for development of a web application (coreapp)
customizing the former web application through a new one (customapp)
being able to develop customapp without the need to have the coreapp sources (hence using the dependency manager)
providing the developer the possibility to install on its local maven cache its refactorings
I noticed some issues, but they may be my fault:
I had to provide a settings.gradle configuration file cause it is needed to resolve deps between projects at the gradle side, but in certain phases its entries have to be commented cause it makes the ide throw tantrum (now I really don't remember in which case, but I can try to reproduce it)
I had to add the dependency to a server runtime cause adding provided deps to servlet and jsp api, eclipse publishes them into the webapp hence leading to problems with jstl (see http://forum.springsource.org/showthread.php?87691-Petclinic-Unable-to-read-TLD-quot-META-INF-c.tld-quot&p=314641#post314641) while without the deps, the validation of tags complains "HttpServletRequest cannot be resolved to a type".
I had to introduce into customapp a linked folder that points to coreapp and map it as a depoyment assembly, cause I've not found other ways to let STS merge coreapp war contents with customapp ones (and make them available even for code completion and validation)
So in order to use the example you should
decompress the archive
import the projects
run gradle install to cache the assembled artifacts
run the coreapp and customapp projects on a local server. Their contents should be available respectively at http://localhost:8080/coreapp/core/ and http://localhost:8080/customapp/custom/ .
About electing a local gradle project to satisfy other projects deps
Project deps without multiproject
Hope it could be a good starting point. Please give it a look and ask me for every missing detail.