Given that many if not most Java IDEs don't make use of a file to keep track of what classes are actually part of a project or workspace, and instead simply include all the .java files in a given directory, how do most folks manage revision control for projects? That is, say I need to rewind back to an older version of a project which didn't include a particular .java file: indeed, it wouldn't compile under that version. How do I avoid having to manually delete files every time I do this? And how would I be able to get an idea of what files were added to the project at what points? The CVS-based revision control systems I've looked at don't seem to support this very well.
> The CVS-based revision > control systems I've looked at don't seem to support this very well.
Which CVS based system did you use? I use CVS and I can do all the things you mentioned here.
Sanjay wrote: >> The CVS-based revision >> control systems I've looked at don't seem to support this very well.
> Which CVS based system did you use? I use CVS and I can do all the > things you mentioned here.
Add to del.icio.us |
Digg this |
Stumble it |
Powered by Megasolutions Inc
