One thing you might consider is that tagging is cheap. In other words tagging a subproject isnt' really that much more efficient that tagging the whole thing. We have a similar layout in svn, and when I need to tag "project-a" at version 2.0.1, I just tag the whole trunk as "project-a-2.0.1". That way you know the state of the whole multiproject, including dependency projects in the tag. I don't think there is much of a downside to this.
Obviously lots of different ways, this is just how I do it. Philip On Thu, Feb 3, 2011 at 9:45 AM, micke <[email protected]> wrote: > > Hi Paul, > thanks for the information. > > Common gradle file and custom plugin(s) might be the way to go, at least I > know there probably isn't anything in there to support settings sharing and > global settings. > > If anyone has any more suggestions please let me know. > > Cheers, > Micke > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Project-organisation-question-tp3368986p3369325.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
