I think you would be better served allowing each sub-project to have its own branches/tag/trunk:
site hivemind1 ... hivemind2 hivemind-framework branches tags trunk hivemind-library branches tags trunk something-not-yet-identified branches tags trunk Also, aligning the folder names with the Maven module names helps keep everything sane. This is the structure I've been working on in Tapestry 5. There' should also be another peer folder, hivemin2/hivemind-project that generates the hivemind2 site and contains the master POM for the other hivemind2 projects. Again, Tapestry5 as the reference. On 1/12/07, Achim Hügen <[EMAIL PROTECTED]> wrote:
Hi, I'm preparing a new repository structure. https://svn.apache.org/repos/asf/hivemind/ site (global site) hivemind1 branches tags trunk hivemind2 branches tags trunk This leaves us room for more subprojects. If nobody objects I will change it later today and post how to switch you local workspaces. Achim
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
