[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Branching recursive over subprojects

From: Stephan <inoeval_at_bobmail.info>
Date: Mon, 11 Feb 2013 23:56:21 -0800 (PST)

Hello,

My projects are organized in separate subversion projects. Dependencies
are realized as external objects pointing to another project:

projectA/
   trunk/
      gui/
      core/
      modul1/ (external object who points to a separat project modul1)
   tags/
      release_1.0.0/
      bugfix_1.0.1/
      bugfix_1.0.2/
      release_1.1.0/
      bugfix_1.1.1/
   branches/
      version_1.0/
      version_1.1/

The subproject modul1 has also subprojects.

modul1/
   trunk/
      functionXY/
      utilities/ (external object who points to a separat project utilities)
   tags/
   branches/

If I release a new version of projectA, I create a new branch (e.g.
version_1.1) and a new tag (e.g. release_1.1.0). Bugfixes are developed
on the branch and saved as tag (e.g. bugfix_1.1.1).

There are two problems:
- If I create a tag with fix revisions of the external objects, the fix
revision is only valid for the direct depending projects (here modul1)
but not for nested projects (here utilities).
- If I make a modification on branch (e.g. version_1.1) of projectA in
modul1, then I must commit it to trunk of modul1. Additionaly I have to
update the fixed revision number of the external object modul1 in
projectA.

Is there a preferred way to solve this problems?

In my opinion for all subprojects a branch should be created if I branch
the top project (here projectA). And when I tag the top project in all
subproject a tag should be created too. Is there a automatic way to do
that?

Thanks,
Stephan

--
View this message in context: http://subversion.1072662.n5.nabble.com/Branching-recursive-over-subprojects-tp178187.html
Sent from the Subversion Users mailing list archive at Nabble.com.
Received on 2013-02-12 09:07:00 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.