Don't get me wrong, I've always been a fan of revision control packages. Many years ago I played with RCS, then moved to CVS. Both worked and did thier jobs, but I never really used themto their peak usuage. Then a few years ago we moved our repositories to Subversion (SVN).... well I wouldn't save move, more as we started from scratch when we realized that no one had commited code to the CVS server for over a year (we also realized that the server had been down almost that long). So any ways we started using SVN. We liked it, it did its job, plus when we started using Trac, it had a nice SVN browser built in.
Anyways, so initially being that I was a fan of Eclipse, I began looking for a plugin. Back then the one I found was Subclipse by Tigris Software. Not surprisingly it work great for my needs at the time, it didn't hurt that it was being developed by Tigris since they also developed SVN.
So SVN it was, we liked it and we've stuck with it. Then when Eclipse Ganymede came out, surprisingly, I couldn't get Subclipse to work. I probably could of made it work, but I didn't feel like figuring it out and I read that the Eclipse team had tapped Polarion's Subversive as the SVN-Team provider. I had trouble there too, and you can read my solution here.
So anyways with the entire group moved to Subversive and all happy with the client, we finally decided to start utilizing one of the start features behind revision control systems... we decided to finally start using trunks and branches.... And why this post.... well I greated my first patch for updating my other trunk....
It was so simple... right click my project in Eclipse, select 'Team'/'Create Patch' it then simply asked me what to compare against, I selected my Trunk, and poof, there was my Patch... so simple, I don't know why we didn't start using these features sooner...
No comments:
Post a Comment