Re: Non-unique tag names across projects that should not be merged during conversion to svn

Michael,

I tried the multiproject conversion approach. Even though it migrates all
the non-unique tags correctly (to different tag folders, such as,
SVNURL/ProjA/tags, SVNURL/ProjB/tags), it did the same for trunk and
branches as well. But that is not the structure I am aiming for. I would
like to see one common trunk and branches at the root. I tried changing the
trunk/branches/tags_path option for each of the project, but it didn't give
me the structure I wanted. I would like either of these two output
structures:

SVNURL/
    /branches
        /<list of all branches, merged from all the projects>
    /tags
        /ProjA
            /Build-1
            /Build-2
            /...
        /ProjB
            /Build-1
            /Build-2
            /...
    /trunk
        /ProjA content
        /ProjB content

or

SVNURL/
    /branches
        /<list of all branches, merged from all the projects>
    /tags
        /ProjA-Build-1
        /ProjA-Build-2
        /...
        /ProjB-Build-1
        /ProjB-Build-2
        /...
    /trunk
        /ProjA content
        /ProjB content

So I suppose I am back to looking at SymbolMapper, SubtreeSymbolMapper? If
so, any suggestions in that area?

Thanks,
Vasanth


Usually if you want separate tags for different parts of your
> repository, you should convert each part as a separate project (in the
> cvs2svn sense) by doing a multiproject conversion [1].  This will create
> {trunk, branches, tags} directories for each project and treat CVS
> symbols within each project as unrelated to each other.  (In your
> example, you will get symbols at $SVNURL/ProjA/tags/Build-1,
> $SVNURL/ProjB/tags/Build-1, $SVNURL/ProjA/tags/Build-2,
> $SVNURL/ProjB/tags/Build-2, etc.)
>
> Michael
>
> [1] http://cvs2svn.tigris.org/faq.html#onetoone
>
>

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2778145

To unsubscribe from this discussion, e-mail: [[email protected]].