compilation areas being ignored? (beaninfo, I think).
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Tue Oct 23 05:28:21 PDT 2012
On 2012-10-23 12:13, Erik Joelsson wrote:
> 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.
Which is a bit weird. I wonder if this due to javadoc or the beaninfo
doclet? The latter has a couple of
catch (FooException e) {
// fail silently
}
which might or might not be the cause of this.
>
> 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.
... unless javadoc can compile these using implicit compilation..? Could
that be possible to arrange using proper command lines?
/Magnus
More information about the build-infra-dev
mailing list