Bug 28625 - Huge number of warnings now generated by JDTCompilerAdapter
Summary: Huge number of warnings now generated by JDTCompilerAdapter
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0.2   Edit
Hardware: PC Windows 2000
: P3 minor (vote)
Target Milestone: 2.0.2   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-18 11:20 EST by Paul Field CLA
Modified: 2003-02-11 06:37 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Field CLA 2002-12-18 11:20:19 EST
Between versions 2.0.1 and 2.0.2, JDTCompilerAdapter has changed the warnings 
produced by the compiler from:

-warn:constructorName,packageDefaultMethod,maskedCatchBlocks,deprecation

to

-
warn:constructorName,packageDefaultMethod,maskedCatchBlocks,unusedLocals,unusedA
rguments,unusedImports,syntheticAccess,assertIdentifier

The addition of the extra options means that running Ant now generates a huge 
number of warnings on our source tree. The warnings are collected in the Log 
Console, which seems to get slower and slower, and our Ant build has become 
impossibly slow (it was less than 1 minute and is now over 20 minutes - at 
which point I killed the process).

We can work around the problem by using the Ant "nowarn" option to disable the 
warnings, but we would ideally like to have some of the warnings turned on.

I'd be happy if the warnings were changed back to those used by v2.0.1. 
However, perhaps it would be possible to use an Ant property to define the list 
of warnings? Ant's jikes wrapper does this for extra options (see the bottom of 
this page: http://jakarta.apache.org/ant/manual/CoreTasks/javac.html ).
Comment 1 Olivier Thomann CLA 2002-12-18 11:43:32 EST
This is fixed in 2.1 stream. Another solution is to recompile the ant adapter
using the source provided with the 2.0.2 build.
Comment 2 Olivier Thomann CLA 2002-12-18 11:49:20 EST
If you specify nowarn="on" and deprecation="on", you will preserve deprecation
warnings. That might be an acceptable workaround.
Comment 3 Philipe Mulet CLA 2002-12-19 06:04:15 EST
Olivier, please post a patch on the JDT/Core page (2.0.2 update).
This is indeed quite painfull.
Comment 4 Olivier Thomann CLA 2002-12-19 08:29:54 EST
I will post a patch today.
Comment 5 Olivier Thomann CLA 2002-12-19 08:58:17 EST
Patch submitted on the JDT/Core development page.
Fixed and released in 2.0.x stream.
Comment 6 Olivier Thomann CLA 2002-12-19 09:00:03 EST
It might help to give the direct link:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r2.0/main.html#updates
Comment 7 David Audel CLA 2003-02-11 06:37:33 EST
Milestone is not correct. Change 2.1 M5 to 2.0.2.