Community
Participate
Working Groups
It seems that most of the project settings go into the ".project" file. However it seems that the if you choose a different java compiler settings (warnings etc.) those do not get stored in the .project file and so if the project is in source control different people will be seeing different warnings on their local copy of projects.
Moving to JDT/Core.
Compiler settings are currently stored in the workspace metadata, waiting for a generic platform preference solution which is being investigated for 3.0. We already store the classpath setting in our .classpath file, and were reluctant to add another preference store file in there (to avoid cluttering). Note that if appending into the .project file, then integrating changes will become really tedious due to multiple separate concerns intermixed.
*** Bug 43090 has been marked as a duplicate of this bug. ***
Closing as preferences are going to be reworked, but not persisted in .project file.
There seems to be a disconnect in communication between the last message and the people filing this bug. The problem is that we WANT the settings in the project file. We want all of the settings in that file so that when developing in teams, everyone is developing with the same settings. I would re-open the bug if I could because it is a relevant issue until the hypothetical reworking of the preferences is not only done but reflects the goals of the poster of this bug. If not, I suppose id have to report it again as this is very important for team collaboration.
It would be pointless to workaround missing shareable preferences when these are going to be provided for 3.0. Why aren't you simply exporting your preferences in some preference file which you decide to share in your project directly ? This would be a workaround which would not require any code change.
