Skip to main content
A
Anonymous
January 28, 2012
Question

Coldfusion with Eclipse, cfeclipse plugin, and cvs

  • January 28, 2012
  • 3 replies
  • 2066 views

Hello. My team of developers is growing and I realized I need to implement version control software to track changes. I setup a Linux Ubuntu server and created a cvs repo successfully. My team is using eclipse for coldfusion development. The problem I'm facing is how to properly setup the files on the web root dev server with cvs. It seems that cvs wants to work with the developer local files only and not the files on the dev server web root. Or maybe we're setting up the eclipse project incorrectly. The way we've set it up is create a new project and then in that new project create a new folder but use the advanced feature to link to an outside folder that is mapped to a drive that contains our dev environment source code. It seems you cannot check out or commit changes to a folder in eclipse that is mapped and linked and not on the local machine of the developer. How do I properly set up an eclipse project that is synced to the files on our dev server that allows my team to checkin and out and commit changes to the files on dev?

This topic has been closed for replies.

3 replies

A
Anonymous
February 1, 2012

Thanks everyone for the tips and pointers. The only version software we were able to get working was CVS so we were thinking of settling on that. now im rethinking it bc of so many people having bad experiences with it.

I gotta say though, this source control stuff is such a pain to learn and setup. I don't know why they don't have something that doesn't require typing in so many damn commands to install and create a repo and sync it. I feel like I'm in 1980 or something with this command prompt Linux stuff. Why can't someone create a step by step wizard that makes it somewhat relatively simple. So many instructions online say to "refer to your subversion admin" but in this case I guess I am the admin! Oh well just venting my frustrations I'll shut up now :-)

12Robots
12Robots
Participating Frequently
February 1, 2012

If you're on Windows and want to use SVN, take a look at VisualSVN Server. It's free, easy, and requires ZERO command line.

Don't be too hard on the command like though. I have been using it with Git (thought I would never it get used to it) and it actually only took me a couple of hours to get the swing of it and I actually now prefer it to the GUI interfaces. Git is easy to set up and use, but if you need to host your own central repo then Git can be a problem, especially on Windows. There are some Git server installers to make it easier, but I was able to let someone else (I use BitBucket for our organization and Github for personal) host it for us.

I think with either SVN or Git you'll be much better off. If you are having problems with installaiton/configuraiton I am sure there are forums just like this one for help with those issues.

Owainnorth
Owainnorth
Inspiring
February 1, 2012

If you're on Windows and want to use SVN, take a look at VisualSVN Server. It's free, easy, and requires ZERO command line.

This.

It's exactly what I use here, and if you're an SVN novice (as I was when I set it up) then it really is all you need. Unfortunately SVN is one of those things you only *really* learn when it goes wrong or you have conflicts. Don't forget you can easily write yourself scripts to do the SVN commands if you have common check in / check out commands you do. After a few months of using SVN, you'll wonder how or why you ever went without it.

Oh, and don't forget to backup your repositories eh?

Prasanth_Kumar_S
Prasanth_Kumar_S
Inspiring
January 30, 2012

I am used to Subversion, but the following comment will be useful in your case too.

  • Version Control is used to manage the different versions of files and to properly merge the changes done by different users.
  • We have to check-out files to local machine when we need the latest  and check-in files to the repository once our changes are finished.
  • In your case, you will need to setup a repository. Then checkout the files to the dev server root.
  • You will also need to have the developers checkout the files to their individual local environments.
  • Once the developers finish making changes, they can commit the files.
  • After all the file changes are committed, you will need to check out the files in the dev server root. Then you will get the latest files in the dev server.

If you are using subversion, you can have an Eclipse plugin (subclipse) for integrating the SVN client to Eclipse so that developers can checkout and commit files right from Eclipse itself. Also, you can automate checking-out latest files to dev server by following the process described here (http://bit.ly/wyFNEP).

12Robots
12Robots
Participating Frequently
January 28, 2012

I don't have an answer to your question, sorry. But I do want to try to help you in another way.

If you and your team are just getting started with Version Control and have the option, you should consider other options before settling on CVS. The fact that you are using CVS suggests that you may not have tried or looked into much else.

CVS is a 20+ year old version control system that is considered poor (by many) compared to the alternatives. Both SVN and Git are better (in mine and many others' opinions) source code management tools that will, in the long run, cause you considerbly less pain and suffering in the management of your code base.

If you have a specific reason to use CVS, or if you just like it, then, by all means, do so. But I have used CVS, SVN, and Git and I can tell you from experience that you are heading down the wrong path. My current VC tool of choice is Git. I started out with CVS and switched to SVN because SVN solved many of the problems CVS had. I used SVN for a few years and did not see a need to give it up, but now that I have been using Git for a couple months I see how much easier it can be to manage a repo. I am not a fanatical Git enthusiast. But I do understand why some people do get fanatical about it. It is *really* a nice tool.

A
Adam Cameron.
Inspiring
January 29, 2012

I don't have anything else useful to add to this, other that to say that Jason pretty much beat me to the same comment, and I agree 100% with what he says.

I've not used Git myself (I am still unconvinced by what it will bring me over SVN for the way I generally work), but a lot of people sing its praises so if I was starting from scratch, that's probably the direction I'd go.  I've used CVS and it's goddawful, and would never wish it on anyone if there was a choice for them to not use it.

--

Adam

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices