[#DIR-102] Add svn:externals to directory

Directory

Add svn:externals to directory

Created: 08/Feb/05 06:17 AM Updated: 06/May/09 03:55 PM

Return to search

Component/s:

miscellaneous

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Resolution Date:

31/Aug/06 08:33 AM

Description

« Hide

It is a bit weird to checkout 'directory' due to the multiplicity of subprojects which each has its own lifecycle (ie branches and tags).

Maybe it would be helpful to use the extremely poorly documented svn:externals option so that the trunk checks out the trunks of each subproject and not the whole trunk + branches + tags

Another option would probably be to move all submodules in the trunk if they don't such have a different lifecycle. TBC.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Brett Porter added a comment - 08/Feb/05 06:55 AM

the reason for the current layout is that each subproject has a different lifecycle.

[ Permlink | « Hide ]

Stephane Bailliez added a comment - 08/Feb/05 08:23 AM

Fair enough, but it looks like you might be going a bit far into decoupling things and thus creating more complexity than necessary in the structure.

It's nearly like instead of having java 'packages' you have been creating sub-modules with a different lifecycle.

I'm not sure there will be such a different lifecycle between sub-modules, especially as there are no resources to do backward compatibility testing and mixing. (there is no QA so it's always HEAD)

Therefore you will nearly always tag each trunk at the same time...which is exactly the same has having all under the same trunk, except that it is much more manageable..you might even get most of them into the main source tree :)

[ Permlink | « Hide ]

Stephane Bailliez added a comment - 05/Nov/05 07:15 AM

[ Permlink | « Hide ]

Alex Karasulu added a comment - 05/Nov/05 01:30 PM

Hey Stephane! This is certainly an option. However I think there might be a better approach to this. Take a look at this Confluence page here:

http://docs.safehaus.org/display/APACHEDS/New+Project+Layout

It explains a new structure that is used by felix which makes a lot of sense. If we use this then the use of svn:externals are not necessary. WDYT?

[ Permlink | « Hide ]

Stephane Bailliez added a comment - 05/Nov/05 07:57 PM

Yes, moving everything in the same trunk leads to what I was suggesting in my initial issue comments in February.

I'm fine with this, even though I'm not quite sure about the tagging policy, but with subversion you can change the layout anytime, so everything will be refined with time. +1 :)

[ Permlink | « Hide ]

Emmanuel Lecharny added a comment - 31/Aug/06 08:33 AM

I think this has been done somehow.

Branches are using svn:externals to point on shared and mina subprojects