Hi: I am a eclipse fan boy too. Currently, using the 3.0 M9. SVN is not too hard to use. I am using Fedora Core 2 (subversion already on the distro) and before on fedora core 1 I needed to install some rpms to make it work, but it was not dificult. Some commands I often use to keep track of what is going on in forrest:
svn up - Update the local working copy svn status - Print the list of changed files in the local working copy. svn ci - commit. It is really easy to use. Also web acces is avaliable. Best Regards, Antonio Gallardo. Patrick Mueller dijo: > Dain Sundstrom wrote: >> >> [X] Yes, switch to SVN. >> [ ] No, stick with CVS. >> >> >> [X] I don't care if the history is imported. >> [ ] I want the history imported. > > Lurker vote. > > As a certified eclipse fan-boy, this is good and bad news. > > Bad news, I've never gotten the tigris eclipse plugin (subclipse) to > work, on Eclipse 3.0M7 or anything later. It doesn't even start up on > 3.0M9 without copying the xerces plugin back into 3.0M9. > > Good news, as more project switch, the onus will be on eclipse to > support this, or someone else may get off their duff and get subclipse > working. > > For eclipse users, this isn't so bad anyway. Being able to co geronimo > from within Eclipse was nice, but is a small part of the development > story; I'd rather have Maven integration than svn integration at this > point. If I was actually checking stuff in, it would be a slightly > bigger pain. > > -- > Patrick Mueller > [EMAIL PROTECTED] >
