I don't know how many Java developers use VSS (I never did for Java development), and the Subversion mailing lists are helpful in such matters as this post, but I'll give this a try anyway, with the hope of picking up just one more tale of what/what not to do.
I'm aware of the VSS to SVN migration tools at http://scm.tigris.org. Does your book offer, or do you have to offer, any hints/tips/tricks on repository migration in general and/or VSS to SVN migration in particular? I want to move some .NET projects from VSS to SVN soon, and I'm looking to draw on the experience of those who've gone before me.
I know this is a zero added value reply but I spent much time on it during a recent conversion and ultimately grabbed the latest version from VSS, started over in Subversion from a new version, and kept VSS around in the unlikely event we needed history from it. (I say unlikely because in our case it is -- not necessarily the case for others.)
Joined: Sep 25, 2000
I noticed that in solutions under control of VSS, the *.sln file shows entries like the one below when viewed with a text editor:
This section is lacking in solutions not under VSS control. Are these sections stripped by the conversion process? If not, does opening the solution cause a connection attempt to VSS? One of my team members is concerned about this. Admittedly, we could just try it, but I thought I'd ask about your experience. Could you check one of your solutions now in SVN and report back whether a section like the one above remains?
Many thanks, Craig
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com