> On Dec 12, 2018, at 6:39 AM, Magnus Ihse Bursie
> wrote:
>
> Yes, the requirement for docs-jdk-index is indeed incorrect. Probably some
> remnant from when I splitted up the single monolitical "docs" target, that
> depended on exploded-image.
>
> Dan, please try if this patch helps you:
> -
On 2018-12-12 02:47, Dan Smith wrote:
On Dec 11, 2018, at 5:28 PM, Erik Joelsson wrote:
- Can we similarly eliminate dependencies from 'make docs'? Right now, the
javadoc invocation requires compiled classes to be available, but I don't know
if that's necessary. Maybe it will work just as we
On 2018-12-12 01:28, Erik Joelsson wrote:
Hello Dan,
On 2018-12-11 15:43, Dan Smith wrote:
Would it be possible to adjust the build system's handling of docs so
that it is not necessary to do a complete compilation before the docs
can be generated?
I'm working with specs, and the followin
> On Dec 11, 2018, at 5:28 PM, Erik Joelsson wrote:
>
>> - Can we similarly eliminate dependencies from 'make docs'? Right now, the
>> javadoc invocation requires compiled classes to be available, but I don't
>> know if that's necessary. Maybe it will work just as well if it only has
>> source
Hello Dan,
On 2018-12-11 15:43, Dan Smith wrote:
Would it be possible to adjust the build system's handling of docs so that it
is not necessary to do a complete compilation before the docs can be generated?
I'm working with specs, and the following command does mostly what I want:
make jdk.jdi
Would it be possible to adjust the build system's handling of docs so that it
is not necessary to do a complete compilation before the docs can be generated?
I'm working with specs, and the following command does mostly what I want:
make jdk.jdi-gensrc hotspot-gensrc && make docs-jdk-specs-only
