Bug 31923

Summary: Source folder specific compiler settings
Product: [Eclipse Project] JDT Reporter: Andrew McCormick <smileyy>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3    
Version: 2.1   
Target Milestone: 2.1 RC1   
Hardware: All   
OS: All   
Whiteboard:

Description Andrew McCormick CLA 2003-02-14 17:26:38 EST 
I'd really like to use the compiler warnings for things like unused private
variables, unused method parameters, etc.  However, my project consists of a lot
of generated code that's generated outside of my control (specifically Castor).
 This generated code contains a lot of these warnings, so the legitimate ones
get lost in the chaff.  I keep my written source and my generated source in
different source directories, so I was thinking it would be nice to be able to
keep different sets of warning/error preferences for different source folder
sets.  I'm not sure how confusing the UI on that would be, though.
Comment 1 Philipe Mulet CLA 2003-02-15 04:57:59 EST 
Currently, you'd have to use different projects to achieve this. Each project 
can have its own custom set of settings.

You can use prerequisite a project on another one's buildpath, so it should be 
what you want. Also note that each project can have its own buildpath, which 
could be useful in case some of your code isn't supposed to see internals of 
the rest of the code your are compiling against.

Source folders can be associated with an exclusion filter and a custom output 
folder. We don't plan to provide source folder level compiler settings.
Comment 2 Philipe Mulet CLA 2003-02-15 05:19:07 EST 
Closing