It will all be checked into a single SVN project.
When I develop (this is a large project) I often check out multiple copies of a given project so I can work on different bugs/features concurrently and check them in separately.
This is one of the issues I had with the Gradle IDE plugin for Eclipse; a single eclipse project with multiple Gradle sub projects in it appears as multiple top-level projects in Eclipse. This prevents me from checking out multiple copeis of the project from SVN: the Gradle IDE plugin gives me errors in Eclipse becaues of all the name collisions.
So I’m hoping to do soemthing different. Still have mutiple subprojects in Gradle but import it into Eclipse as a single project with a single .project and .classpath file.
The alternative (and I would appreciate educated opinions on this since I’m new to Gradle) would be to not use subprojects in Gradle at all. Just have everything in a single root project.
The other reason I was considering decomposing it is that we are building a web-services application with JAXB code generation, etc. I’m thinking one subproject that produces a beans.jar generated from JAXB, another one dependent on the first that defines/generates the SOAP services interfaces, and a third (dependent on the other two) where we put our application code that implements all the interfaces.
Am I overthinking this? Should I just keep it as one project? Or should I figure out some way to accomplish what I originally asked, even if I have to manually define dependencies the root build.gradle file?