Community
Participate
Working Groups
I had over 2 years of code inside my E:\Programming directory i created a new project by checking it out from CVS into e:\Programming because i figured it would create a new folder inside it i accidently checked it out to e:\programming\com\otherfolders.... when it should have been e:\programming\halo43\com\... well, eclipse decided to erase EVERY FOLDER AND FILE inside e:\programming i had my most important things backed up, but i've lost countless hours of work now because of such a stupid bug. IF THE FOLDER ALREADY EXISTS, DO NOT ERASE THE FILES INSIDE THE GOD DAMN FOLDER. thanks.
The folder could map to an obsolete package, which should be flushed. However, we clearly should warn the user before scrubbing. Alternatively, we should refuse to build if .classpath is missing. Do you remember if this was the case ?
all i did was check out to a folder as project from cvs
We should refuse to build if .classpath file is missing (not defaulting to empty CP).
Alternatively, we could report a task Classpath problem when it occurs, which would cause the builder to not perform either.
Tristan, I'd like to understand the scenario you ran into. When you did check out as project, was it as a simple project, or as a Java project?
If it was a Java project, a Java project wizard is now shown where you can enter the output location. This creates a .classpath file. Also added classpath missing marker creation if a project is checked out with the Java nature but no .classpath file.
i checked it out, then in a pop up dialog it says what would you like to do, so i choose a java project. it then asked what would you like to name the project. below that, there is a checkbox that allows you to specify a directory other than ecplise\workspace\fileshere
Verified.
