Hierarchical multi-module projects in a source code repository

[Trevor Harmon]

Hi,

I have a multi-module project that is stored in a flat directory  
structure in our source code repository (Subversion). For example:

repo
    parent
        trunk
        tags
        branches
    child1
        trunk
        tags
        branches
    child2
        trunk
        tags
        branches

Note that parent, child1, and child2 are all on the same level. I  
would like to change this organization so that child1 and child2 are  
children of the parent. This is the usual way of organizing multi- 
module projects, since it makes their relationship clear.

But what about the problem of repository branches? For example, if I  
make child1 and child2 children of the parent, it will look like this:

repo
    parent
        trunk
            child1
                trunk
                tags
                branches
            child2
                trunk
                tags
                branches
        tags
        branches

This is clearly an invalid directory structure (from a repository  
perspective) because the parent's trunk includes the children's  
branches.

So, will I simply have to give up child branches if I want to use this  
kind of hierarchy? I am loathe to do this, since it would force the  
children to have the same version as the parent. Perhaps my current  
organization -- that is, flattening the module directories so that  
they're all siblings -- is the only way to do it... Any thoughts?

Thanks,

Trevor


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org