Just to pipe in that you can also go the other route and structure SVN
to match your projects. There's no reason you can't have subdirs under
tags or branches. We do this all the time both where I work and in my
open source projects.
So, instead of:
repo/tags/v1.0.1
project-a
project-b
You can have:
repo/tags/
project-a/v9.6
project-b/v2.1
You may have other reasons for not doing that but in practice it works
pretty well... and solves the gradle problem.
-Paul
P.S.: On the other side of it, regardless where you put your projects in
SVN you could still check them out side-by-side. Though, I guess with
either of these approaches your build gets tricky as everything versions
at different rates. It might be better to treat them as separate
projects after all. :)
...and if I'm reading your last bit right, you can pull in a shared
common.gradle file or something into your various build.gradle project
files.
On 2/3/2011 4:03 AM, micke wrote:
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
