Hi
I have a couple of questions regarding best ways of organising a set of
projects which needs to be in their own svn folder structure.
Currently we have a multi-project like this:
repo/trunk/
build.gradle
settings.gradle
project-a/build.gradle
project-b/build.gradle
....
project-n/build.gradle
This has worked pretty well but we have realised that we have a need to tag
and brancheach project separately and plan to move it to the following
structure (not showing branches and tags):
repo/project-a/trunk/build.gradle
repo/project-b/trunk/build.gradle
...
repo/project-n/trunk/build.gradle
My initial thoughts are that this will not work with a Gradle multi-project
setup anymore, is this correct?
If a multi-project setup isn't an option I'm wondering if there is a way of
doing something similar to a maven parent project so we don't have to
duplicate everything in each project.
Currently the only thing I can think of is having another build specific
project which has some convenience methods for configuring the projects....
Any advice on this would be great!
Many thanks,
Mikael
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Project-organisation-question-tp3368986p3368986.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
