Listening to: Underworld - Cowgirl
Thursday, 5 February 2004
Fighting the good fight
I was able to get CVS working at work today. Sort of. I got it working with Tortoise, but not yet with Site Developer 5 (WSAD). Before, I narrowed it down to the cvs binary was not on the path when the tool logged in, so it could not find anything to actually run, so it just returns with an end of file (EOF) or IO Exception in WSAD. It took me so bugger long to find that. I don't even know where the path is set for when you try and do a cvs call (command line) from one machine to another. I ended up just making a soft link from where it was on the path, to where the binary file actually installed to. That problem took me much longer than it should have. The IT guy was too busy to help, and I also was playing around with other stuff like making a user (hard if you do it wrong the first time and are trying to figure out how to fix it with the command line). There are other issues that I think that I have to resolve with for using WSAD. I already downgraded the version of CVS because of a problem when they changed what text is passed to the client. I think that tomorrow I am going to dig through the Eclipse code to see how they are (used to?) contacting the server. I still might have a path problem, I am not sure. I don't know if the cvs client that comes with eclipse gets any path info, or looks in a specific directory. We'll see what happens...
Subscribe to:
Post Comments (Atom)
As far as I know, WSAD doesn't add anything to the Eclipse CVS plugin. So find out what version of Eclipse your WSAD 5 is built on (2.0?) and look for CVS bugs with that too ... there is probably more information on Eclipse, and maybe even a patch or update.
ReplyDeleteWhy not use dreamweaver?
ReplyDeleteuhh, whoever asked about dreamweaver, I don't think that you can built J2EE apps with it. I really don't think so. Please correct me if I am wrong.
ReplyDeleteWSAD is built on Eclipse 2.0 (or 2.1? not sure). But if you check out that bug I linked to, they have a solution there. I still think that it's a path problem. I'll let everyone know. ;-)