Bug 77042 - Provide a mechanism for per-project PDE compiler settings
Summary: Provide a mechanism for per-project PDE compiler settings
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.1 M3   Edit
Assignee: Konrad Kolosowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 77021
  Show dependency tree
 
Reported: 2004-10-26 14:19 EDT by Douglas Pollock CLA
Modified: 2004-11-03 22:53 EST (History)
1 user (show)

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 Douglas Pollock CLA 2004-10-26 14:19:03 EDT 
I200410260800. 
 
PDE has recently increased the error level for a bunch of their warnings.  
Unfortunately, this causes problems with our tests plug-in, as it purposefully 
contains some broken uses of our extension points.  It would be nice to be able 
to chose less stringent compiler settings for our tests plug-in.  Much as we 
are able to do with the Java compiler settings. 
 
It would also be nice to be able to share these settings via CVS in a similar 
manner to the Java compiler settings.
Comment 1 John Arthorne CLA 2004-10-29 11:31:40 EDT 
+1 

Core team also has several invalid extensions in its test projects for the
purpose of testing invalid extensions. We can get rid of this by tweaking the
PDE compiler settings, but then each team member needs to do it, and we lose the
benefit of these errors in non-test projects.
Comment 2 Wassim Melhem CLA 2004-11-03 22:53:00 EST 
Marking as fixed.  Thanks Konrad.