Bug 54814 - Per project compiler settings should be stored in file.
Summary: Per project compiler settings should be stored in file.
Status: RESOLVED DUPLICATE of bug 59258
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.1 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-15 09:32 EST by Boris Pruessmann CLA
Modified: 2005-01-11 11:02 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Pruessmann CLA 2004-03-15 09:32:17 EST 
Compiler settings that were changed on a per project basis should be stored in the .project file (or 
similar) so that they can be shared when using an SCM system.
Comment 1 Boris Pruessmann CLA 2004-03-15 10:39:34 EST 
Just for pointing out the use of this: we're running workspaces with about 100 projects and some 
agreed upon compiler settings. However, there are one or two projects with code that was generated 
and compiling this code with the global options results in about 8000-10000 problem markers, making 
Eclipse quite sluggish.
Comment 2 Philipe Mulet CLA 2004-05-10 05:37:20 EDT 

*** This bug has been marked as a duplicate of 59258 ***