>I am leaning toward (1), since branches and tags are cheap in svn and >since, in many cases, you'd like to branch/tag the whole repository. >If you have ideas about this, definitely let me know.
My 2 cents. (1) is much, much easier to manage. Pick (1) if you suspect that you will release the whole system, because then you would want to tag the entire system. (1) is better for branches that change code in modules like hackyCore_Kernel because there will be a ripple effect. (1) You will have a easier time associating Hackystat metrics with a single Hacksytat project when the workspace root changes (ie. C:\svn\hackystatBranch1\) instead of each top level workspace (ie C:\svn\hackystat\hackyCore_Kernel-Branch1). Pick (2) if you suspect that you will release modules. Um.. and I can't think of any others.. > I am going to spend the next several days working on getting > org.hackystat.core.* > imported into SVN and running under the new build system. At that this is probably a very minor issue, but I'm not sure that you want to import files into subversion with the already expanded $Id$. Subversion deals with these keywords differently than CVS. I think you we would have edit a client side config file, in additon to setting a another property. I'm trying to figure out the process to get that working. Anyway, you might want to test that out before having to fix every single file later on just to get the $Id$ keyword working. thanks, aaron
