compilation areas being ignored? (beaninfo, I think).
Erik Joelsson
erik.joelsson at oracle.com
Tue Oct 23 03:13:15 PDT 2012
I believe the reason for the errors, which I'm pretty sure have been
there all the time in build-infra, is a difference in the classpath used
to run the javadoc doclet. The old build adds the main classes dir while
the new build does not. The problem is that the new build couldn't add
it anyway since it's empty at that point in the build. The good thing is
that it doesn't seem to affect the output since we still compare all
classes in the resulting image as equal.
The build would fail if javadoc exited with non zero, which it
apparently doesn't.
It would be nice to avoid these errors. This would require compiling
these sun.util.locale.provider.LocaleProvider* classes explicitly before
running the doclet. Feels like a hack to me though.
/Erik
On 2012-10-23 00:59, Magnus Ihse Bursie wrote:
> The beaninfo stuff uses javadoc. The warnings from beaninfo stands out more clearly when the rest of the output is kept to a minimum. However I know Fredrik changed some javadoc flags on beaninfo to get it to report less warnings.
>
> I'm not really sure why it says "error" but then treats it like a warning.
>
> /Magnus
>
> 22 okt 2012 kl. 18:59 skrev Alan Bateman<Alan.Bateman at oracle.com>:
>
>> I sync'ed up my clone of build-infra/jdk8 today, blew away the build directory and re-built.
>>
>> I noticed one curiosity in the build output:
>>
>> :
>>
>> Cache: Table size 32 (5 bits), shift 1, max chain depth 3
>> Generating beaninfo
>> /u/alanb/ws/build-infra/jdk/src/share/classes/javax/swing/JSpinner.java:43: error: package sun.util.locale.provider does not exist
>> import sun.util.locale.provider.LocaleProviderAdapter;
>> ^
>> /u/alanb/ws/build-infra/jdk/src/share/classes/javax/swing/JSpinner.java:44: error: package sun.util.locale.provider does not exist
>> import sun.util.locale.provider.LocaleResources;
>> ^
>> /u/alanb/ws/build-infra/jdk/src/share/classes/javax/swing/JSpinner.java:45: error: package sun.util.locale.provider does not exist
>> import sun.util.locale.provider.LocaleServiceProviderPool;
>> ^
>> Compiling 4 files for BUILD_BREAKITERATOR
>> Generating HTML DTD file
>> [Parsed DTD html32 in 377ms]
>> Generating BreakIteratorData
>> Generating BreakIteratorData_th
>> Compiling 8969 files for BUILD_JDK
>>
>> I don't know this area of the build but I assume that it's a supporting tool for the Swing bean info classes fails to be compiled. The concerning thing is that this is a compilation error and I would have thought that it would cause the build to fail?
>>
>> I can't say if this is new, the default verbosity has changed since I last sync'ed up which might explain why I didn't see it before.
>>
>> -Alan
More information about the build-infra-dev
mailing list