hilco wrote: > >> If your projects genuinely are stand-alone projects then I would suggest >> that you create separate repositories for each of them, although that may >> be >> harder to do if you already have history within an existing repository. I >> have not done so, but I imagine that it must be possible to clone a >> repository and then remove extra stuff from each copy such that you >> reduce >> to 1 project per repo? > > You shouldn't create multiple repositories without *very* good > reasons. Multiple repositories just means having to duplicate > authentication, backup setup, etcetera. Moreover, any kind of copying > between projects is much harder that way. If you are working on > multiple projects you'll eventually run into refactoring cases where > you want multiple projects to reuse some shared code. That's a > no-brainer in one repository but all but impossible (i.e. without > losing history) in multiple repositories. > >
No problem with authentication and backup in our hands - its perfectly possible to run multiple repositories within the same setup on the same machine. Some would also suggest that your use case of shared code screams out for a new artifact in its own independent space and shared across the projects that way. hilco wrote: > > And what do you gain? There's little advantage to having a repository > per project. > > Independence of code, security from accidental updates whilst the entire repository is checked out.... :o} Like perl, there's always more than one way to do it in the maven and subversion world. And no way is right or wrong as long as it works for you (or doesn't). Later, Andy -- View this message in context: http://www.nabble.com/trunk-tags-branches%3A--root-vs.--project-level-tp19989397p19996403.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
