Different javac options for explicitly and automatically compiled files

[Alexandre Boulgakov]

On 8/2/2011 12:45 AM, Kelly O'Hair wrote:
> Eventually, we should always be using -implicit:none
> That will be part of the build infrastructure changes.
Is there a bug tracking this? That way I could omit the -Werror flag for 
now and reference the relevant bug.

Thanks,
Sasha

>
> I'm talking to Fredrik today, and this week. Hopefully we can get this project more public and
> accelerated.
>
> -kto
>
> On Aug 2, 2011, at 1:02 AM, Jonathan Gibbons wrote:
>
>> On 08/01/2011 02:55 PM, Dr Andrew John Hughes wrote:
>>> On 11:07 Mon 01 Aug     , 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?
>>> It sounds to me like there's a bug there; those files should be being
>>> dealt with earlier in the build or as part of java/net/Makefile.
>> Regrettably, there are circularities in JDK :-(
>>
>>> If they aren't implictly compiled from the source tree, then presumably
>>> classes from the bootstrap runtime library will be used if present, which
>>> could cause all sorts of issues.
>> No. The Makefiles should be set so that the "bootstrap runtime library" is overridden
>> with -bootclasspath, meaning that the compilation will fail if the classes are not
>> available to javac in source or compiled form.
>>
>>>>> Thanks,
>>>>> Sasha