Oh, I just saw this post: https://coderanch.com/t/570391/vc/Finding-Workspaces-Directory Is that what you are asking about? If so, then yes, just create a new workspace and import the projects into it. You might want to clean up the existing projects first, though. By clean up, I mean remove all created files (.class, .jar, etc.). You do this because all you really want to import are the source files. (By the way, this is the mechanism used in development shops where sources are stored in a version control system such as Subversion.)
Another alternative is to simply create new projects in your workspace and copy the sources from the old projects into the new projects. I usually do this when I am changing the build mechanism (usually to using Maven).
Ask Eclipse to build them (actually, unless you turn off auto-build within Eclipse, it builds them automatically). Unless you have an Ant or Maven build script (highly recommended), in which case you would use that.
CVS is a version control system, just like Subversion. Eclipse even has built-in support for CVS. If the sources are already in CVS, as long as you know the repository URL for the project, you can have Eclipse import the projects.
Michele Smith wrote:how can I tell if the previous developer used ant, and also how can I also utilize ant?
Is there a build.xml file in the base directory of the project? If so, then Ant is used to build the project. (If, on the other hand, there is a file name pom.xml, then Maven is used as the build tool.)
If there is no build.xml file, you can always create one yourself. The advantage of doing so is that you can then set up a Continuous Integration environment where your project is built using an automated build process of a build machine. On the other hand, if you are the only person working on the project, and you don't mind doing builds manually by yourself, then you don't really need an Ant build script. (In our shop, all developers commit their sources to Subversion, then we use Jenkins to compile those sources on dedicated build machines. We use Maven for all of our builds. Developers are free to build things on their PCs, but such builds are never used in production - only builds performed by Jenkins ever go into production.)
Hello I understand what you mean now. I just have one last question related to this post and that would be:
after you have located the ant script and made any necessary edits, what steps must you undertake to build the project? If it is a web project, it must have a server, right? Then you can build the project utilizing the Project/Build All with the ant script to get the necessary .class files et al etc?
Is this correct or am I incorrect and need some re-work on this?
Which one you do depends on whether you want to do a clean before a compile or not. If you don't do the clean, only the changed code will re recompiled. Not that recompiling only changed code has the possibility of causing various problems. Personally, I always clean and then compile.
Back to the "how to compile" question, you might be able to compile from within Eclipse, but that all depends on whether the Eclipse project is set up to use Ant to build the app. To find that out, right-click the project in Eclipse, select Properties and look under Build. If one of the Builders has an icon that looks like an ant, then Ant is being used for the build.
After the build, there will be either a directory containing the web app contents, or there will be a WAR file (based on your build.xml, there is no WAR file). Deploying the app requires that you copy the web app to the server.