Creating a subversion trunks folder in JBoss Common

[pgier]

I'm not sure if this is the right forum for this, but I would like to create a trunks folder at the root of the JBoss commons project. It would use svn externals properties to map to each of the subproject trunk folders. This would allow us to keep separate the trunk/tags/branches separate for the subfolders, but also allow an easy checkout process.

Currently we have to check out each common subproject trunk folder separately. If I create a folder called "trunks" here:
https://svn.jboss.org/repos/common/trunks

I can put one svn property that maps to the trunk folder of each of the subprojects. So that all the subproject (common-core, common-logging-jdk, etc) trunk folders can be checked out at one time.

For more information about how this works you can look here:
http://svnbook.red-bean.com/en/1.1/ch07s04.html

[starksm64]

The reason why it was not done this way originally was to allow for separate releases of these projects. I guess your just talking about simplifying the situation where you want to pull down all the projects together as a group. That sounds fine.

[pgier]

Yes, it's just for convenience. You would still have a trunk folder for each subproject, and you can still do separate releases. I'll just add an additional "trunks" folder that contains a link to each of the trunks.

I noticed that this is how the maven svn repository is setup, and it seemed like a nice idea.

[pgier]

I noticed that the trunks folder does not work when accessing svn through the anonymous URL because the aliases are all pointing to the https url.

Do we need to have a separate anonymous URL? I've set up subversion in the past where read access is anonymous, but when you try to commit, you are prompted for a password. This way you can have both types of access without 2 URLs.

[starksm64]

Talk to it about why it was setup the way it was. I don't know if bandwidth was a concern.

Sounds like svn needs a replication tool that allows for link url rewritting.