On 2/3/2011 3:20 PM, Mikael Andersson wrote:
Thanks to everyone for your comments. I'm not to worried about versioning, haven't actually nailed down how to perform that and releases yet (except for the fully manual approach)... My main motive for this question was to figure out how to reduce duplication of build script code which I currently have in the top level build file (uploadArchives, javadoc/source jar tasks, integration test tasks/configuration, checkstyle tasks, cobertura tasks, global variables for library versionsing, etc. etc.). This is the kind of stuff I was hoping there was support for in Gradle. Will probably end up implementing what you guys have suggested, a common.gradle file, still don't think that is optimal though since
I have this issue with one of my open source projects, as well. Lots of independent sub-projects with one common.gradle file, and yeah, I have to make sure to pull it in with my tags for each project.
that file should be version controlled and will have to somehow be synced across developers machines, ci server, and build machines... Or is it possible to pull a script like that in from a repository?
I do this with some other plug-ins that I have checked in SVN. Since sourceforge's SVN is accessible from HTTPS, I just use the specific version URL in the 'apply' and so I can peg it at a specific version. I may end up doing that for my common.gradle, also now that I think about it.
-Paul
Many Thanks, Mikael On 3 February 2011 09:03, micke<[email protected]> 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 -- 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--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
