Bug 108553 - Ability to exclude pkgs from Compiler "warning" and annotation processing
Summary: Ability to exclude pkgs from Compiler "warning" and annotation processing
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement with 6 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 242402 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-01 03:44 EDT by Missing name CLA
Modified: 2008-08-22 13:56 EDT (History)
4 users (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 Missing name CLA 2005-09-01 03:44:37 EDT 
Eclipse does a great job with "Errors/Warnings" processing.

Our projects use jaxb and other code generators. In the dev phase this is all in
one project (i.e not in supporting jars ).

The compiler "Errors/Warnings" processing option applies to these sources as
well. We need an ability to exclude pkgs from the "Erros/Warnings" annotation
processing.

We obviously need the files to be compiled.

Although we apply suppress warnings temporarily they are lost on src
regeneration which is frustrating.

Please treat this as a critical enhancment. 

Cheers and goodwill.
Comment 1 Missing name CLA 2005-10-15 17:52:20 EDT 
I have had no feedback on this. What do Eclipse developers think ?
This is a critical enhancement for those of use using code generation.

Any chance of this being included in 3.2 final release ?
Comment 2 Daniel Beland CLA 2007-05-03 05:39:21 EDT 
I would also like to be able to exclude folders. Some generated code share the same package as my code and I want to exclude the generated only which reside in a different folder.
Comment 3 James Sutton CLA 2007-05-04 06:26:49 EDT 
I should like to be able to set specific warning sets per package or per file. We have some auto-generated source files in our project and they have warnings which don't matter and we cannot do anything about anyway. So we want to disable the warnings for these but maintain the normal warnings for all the other files in the project.
Comment 4 Jerome Lanneluc CLA 2008-08-22 11:49:07 EDT 
*** Bug 242402 has been marked as a duplicate of this bug. ***
Comment 5 Damien Cassou CLA 2008-08-22 13:56:14 EDT 
I have the same problem.