Different javac options for explicitly and automatically compiled files

Jonathan Gibbons jonathan.gibbons at oracle.com
Mon Aug 1 21:47:36 UTC 2011

.. and no, you cannot selectively enable -Werror, except by separating 
the work into multiple compilations.

You could (uugh) put @SuppressWarnings on the unfixed classes as an 
interim measure, if you were certain it is only an interim measure.

Otherwise, you could fix those other warnings too, which would be the 
best solution ;-)

-- Jon

On 08/01/2011 12:27 PM, Joe Darcy wrote:
> Hi Sasha.
> This isn't the question you asked, but you can use
>     javac -implicit:none
> to disable the compilation of implicitly referenced types.
> -Joe
> On 8/1/2011 11:07 AM, Alexandre Boulgakov wrote:
>> Hello Kelly,
>> Do you know the answer to this one?
>> Thanks,
>> Sasha
>> On 7/29/2011 11:37 AM, Alexandre Boulgakov wrote:
>>> Hello,
>>> I am working on removing the javac -Xlint warnings from java.net.*. 
>>> After removing these warnings, I would like to turn on javac's 
>>> -Werror flag in make/java/net/Makefile. However, it seems that the 
>>> javac task in make/java/net/Makefile has to automatically compile 
>>> some dependencies (not listed in the makefile, presumably inferred 
>>> by the compiler from the sourcepath) which have not had warnings 
>>> fixed yet (sun.net.idn.*, com.sun.security.ntlm.*).
>>> Is there some way to have the -Werror flag only apply to explicitly 
>>> specified source files, but not to the ones that javac pulls in 
>>> automatically?
>>> Thanks,
>>> Sasha

More information about the build-dev mailing list