Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339817 - reconsider access warnings
Summary: reconsider access warnings
Status: RESOLVED FIXED
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: 3.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.10.0   Edit
Assignee: David Williams CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-13 01:35 EST by David Williams CLA
Modified: 2018-06-29 15:30 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2011-03-13 01:35:09 EST
Since we turned off "customize access warnings" The total number for a full build jumped from 60K to 120K ... either number is too large to be of much use. 

Worse, probably, is that using the "+discouraged" in compilerArgs adds about 80Meg to size of main logging file (which echos the individual compiler warnings for each component compiled). That is not only unmanageable but must slow things down in processing, IO, etc. 

So, I propose we "turn off". Very easy to do that ... just use -discouraged in
compilerArg, which is in biuld.cfg ... I guess there since we thought these might vary by stream ... but, don't think they do any longer. 

compilerArg=-showversion -encoding ISO-8859-1 -warn:-serial,-raw,-typeHiding,-unchecked,-discouraged

The harder part is improving our custom ant task that scans files for these, and provides summary counts. Without fixing that, the summary page would just show "0" for all of them ... which seems kind of misleading.
Comment 1 David Williams CLA 2011-05-12 13:37:10 EDT
we did stop flaging these (I think output still needs to be improved, to not show "0") since could be confusing to casual readers.
Comment 2 David Williams CLA 2011-05-12 13:56:12 EDT
I cloned 345634 to cover the improved output in the future.