Peter, Ken,
Thanks for the responses. I asked the question on a Friday afternoon, after
a long week, and without a recent cup of coffee. Right after submitting the
question to the list, I was talking it over with a co-worker and she pointed
out that it was a pretty silly/stupid idea. At that point, it finally
dawned on me that I was so heads down trying to break up a monolithic
project that I wasn't seeing the forest for all those pesky trees. The
projects are indeed related and I'm now using a more traditional (though
still probably SVN-centric) layout:
moduleA
branches
tags
trunk
monolithicProj (shrinking)
moduleB
branches
tags
trunk
projA
projB
projC
(more to come)
Thanks for your time, patience, an excellent explanations.
Jamie
On Mon, Mar 14, 2011 at 3:53 PM, Ken Sipe <[email protected]> wrote:
> Jamie,
>
> I didn't see an answer to your question... The short answer is yes, gradle
> can work with that setup, however it would be confusing and I'm not sure
> what the advantages of your setup are assuming foo is the root or master
> project. You would need to be able to select which "tag" you wanted for
> each project which would make for a complex build script at foo for
> questionable value. Also... this seems very SVN centric... if you moved to
> git in the future... you would never do anything like this (although you
> might see sub-project builds with different versions if that is your
> intent). One of the more interesting problems with this setup is if foo is
> your master project, then this setup would add addition challenges to
> version the build script at the foo directory level.
>
> If on the other hand your master project is projA, then again Gradle can be
> configured to handled that.
>
> Ken Sipe | [email protected] | blog: http://kensipe.blogspot.com
>
>
>
> On Mar 11, 2011, at 12:18 PM, Jamie Bisotti wrote:
>
> > All of the multiproject examples I've come across seem to assume the
> following VCS structure:
> >
> > branches
> > ...
> > tags
> > ...
> > trunk
> > foo
> > projA
> > projB
> > projC
> >
> > However, what about the following alternate structure:
> > foo
> > projA
> > branches
> > tags
> > trunk
> > projB
> > branches
> > tags
> > trunk
> > projC
> > branches
> > tags
> > trunk
> >
> > Anyone doing anything like this?
> >
> > Thanks,
> > Jamie
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
--
Jamie Bisotti
