Hi Stefan, we use one repository per project, and within the project there are several modules and all of them have a trunk/branches/tags directory. Our structure is like this:
repository project 1: module1/branches module1/tags module1/trunk/pom.xml module2/branches module2/tags module2/trunk/pom.xml repository project 2: module1/branches module1/tags module1/trunk/pom.xml module2/branches module2/tags module2/trunk/pom.xml With kind regards, Simon von Janowsky -----Ursprüngliche Nachricht----- Von: Stefan Fritz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 15. Oktober 2008 10:49 An: Maven Users List Betreff: trunk/tags/branches: root vs. project level Hi all, we are in the process of restructuring a subversion repository and "Mavenize" all projects. The main discussion at the moment is whether to have trunk/tags/branches on the root level or once per project. root: trunk/project1/pom.xml trunk/project2/pom.xml branches/branch1/project1/pom.xml project level project1/trunk/project1/pom.xml project1/branches/branch1/project1/pom.xml root level: pro: all branch/patch related projects in one location easy to navigate easy to update cons: does mvn release:branch work ? mergin can get hard if somebody commits at root level project level. pro: easy to work with mvn release merging should be easy cons: complex for scenarios where you have to deal with multiple projects at once Would be curious about your opinions/comments! Thanks Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
