I'm working with a project that's stitching together a bunch of modules through
svn:externals commonly checked out into a 'known' structure. This means that I
can't introduce code at the root directory of the checkout, unfortunately, and
that seems to be the standard way of describing a hierarchical multiproject
java build in Gradle.
Is there anyway that a settings.gradle file, and consequently all of the
related modules, can refer to sibling directories in the project layout? For
example:
-\module1
-\module2
-\...
-\gradleRoot
I tried the naive approach of just adding relative paths to the module names in
settings.gradle, but it looks suspiciously like that changes the actual names
of each module, breaking intermodule dependencies.
I know the ideal answer is to have one cohesive branch to commit the code in,
but that isn't an option available to me - at least not in the short term.
Any help would be greatly appreciated!
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
