Here is my point of view about this. > > [snip] > > > > To the point: I'd like to move some directories around. Is it ok > > > if I create a branch containing the new directory structure + pom.xml > > > files, possibly using symlinks (yes you can version those > > > too nowadays, I believe) to point to the real source directories? > > > > Here's the issue I see with this approach: Cactus developers and users are > > not going to use the Maven2 build system before it is fully functional and > > before it allows to fully build Cactus. This won't happen overnight > > either... :-) > > Indeed. That's why I suggested a branch, so I can incrementally 'save' my > work and let you guys check it out, while in the mean time you can > continue working.
I am with Kenney for this. And the symlink idea is great for me. > Summary: > > Working in trunk: > ------------------ > Pro: staying up to date, no merge issues > Con: it'll probably break some builds as I'm not too familiar with the > codebase yet and it might not run tests or something.. > Con: I'll probably make it harder for the people who have outstanding > commits, and for myself, when I move directories around. Depends on > the work-commit rate/interval. > Con: (for me) initially more work because i'd have to update the > ant buildsystem first As I have play with it ;-) I can probably help you for this part... > Pro: while updating the ant build system I learn how it works and know > what needs to be done in m2. > > Working in a branch: > -------------------- > the opposite of the above.. :) - staying up to date, no merge issues Didn't using symlink invalidate this con? To conclude, I am for a mixed solution : working on a branch with symlink and when one of the Vincent's step is attain applying the change to the trunk. Nicolas > > > -- Kenney > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
