Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090910 Ubuntu/9.04 (jaunty) Shiretoko/3.5.3 Build Identifier: 20090619-0625 When you are working on a non-eclipse based project (such as git or jgit) there is no .project file, and either refreshing or opening a project in this state in eclipse causes it to fail on the project and close it. I would propose that a better behaviour in this case would to be to just treat the project as a "General" Project. This is VERY frustrating and annoying when I'm trying to use eclipse to edit projects like this. I have to stash the .project file away for most commits and updates. Reproducible: Always Steps to Reproduce: 1. Create a general project 2. Close the project 3. Remove the .project file outside of eclipse 4. Re-open project 1. Create a general project 2. Remove .project 3. Refresh the project.
Eclipse needs that .project file, as it contains all the info about the project. Deleting it externally and expecting Eclipse to work fine is not fair :-) You should either checkin the .project file or add it to the 'ignore list' (the equivalent of .cvsignore in your repo) and have it locally.
Actually I think he has a point. It's reasonable to allow the project to open in the event that the .project file is missing. But it's not our decision.
I would use Prakash hint. Some resources facilities like linked resources, builders and natures need .project. Projects without the description file would probably have limited number of operations. However we could perhaps create .project on demand.
@Szymon Brandys: Somthing like your last sentence is all I'm asking for. @Prakash G.R.: When it's a "Generic Project" the only item in there is the project name which isn't even respected, and I'm fine with no builders. Also on some open source projects, people don't want you putting in .project into the ignore files and commiting those ignores. At least if I have a basic project (a glorified file explorer) I can read my files with my eclipse editors and fix conflicts. This mainly comes up when doing things like rebases in git, but also when updating in SVN.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
