I just checked out some projects from svn to my pc, and I tried to import the projects into my workspace. But I failed to import some of them, and eclipse didn't recognize those projects(didn't show up in the import window). And then I turn to google and found a solution -"add .projects and .classpath file to project folder" works. However, what make me really confusing is that I foundthe projects I successfully imported into workspace without manually adding the files for them also don't contain .projects and .classpath. Eclipse just create the files for them automatically after import, so it seems that the fail of importing projects(or recognizing projects during import) is not just simply because of the lack of .projects and .classpath. Does anyone know what cause the difference? How does eclipse exactly recognize a project as importable project? *eclipse version info here
0
votes
Imported how exactly? Import Existing Projects doesn't even show the project in the dialog if it does not have a .project file (.classpath doesn't matter). Don't forget that on some systems file names starting with '.' are not displayed by default. Also note that Eclipse Galileo is now 11 years and 17 releases old.
- greg-449
There are different ways to import projects. For a couple of years Smart Import has been introduce to detect and configure projects. But your Eclipse version is even older and the question is, why do you do retrocomputing?
- howlger
@greg-449 For some reasons about my job, I'm not allowed to use a newer version... Thanks for the reminder. I've checked that the .project will be showed if it's there
- Ting Chen
1 Answers
0
votes
Eclipse or any other IDE doesn't required .classpath or .project files. These files will be auto created during the project import. IDE can capable to pull the artifacts from maven central repo automatically by using build descriptor file such as pom.xml or build.graddle.
The files .classpath and .project will store the paths from local machine, if we carry them to another system, the artificats and other dependencies may not be present in the same directory, so it will start complaining build errors. Thats why while committing to GIT always there is .gitignore, so that local configuration will not carry to others while contributing.
