2018/5/3 13:16:11 +0100, volker.simo...@gmail.com:
> On Thu, May 3, 2018 at 12:21 PM, magnus.ihse.bur...@oracle.com wrote:
>> ...
>>
>> Until a consensus of a better solution for hosting the generated
>> documentation is reached, I'd like to avoid changing the build code. That
>> will just open fo
On 2018-05-03 13:21, Magnus Ihse Bursie wrote:
> A lot of links on the interwebz are pointing to the docs at
> docs.oracle.com, and it would probably be quite messy if the same (or
> even worse, almost the same) documentation were published both at
> docs.oracle.com and java.net.
Well, until qu
On Thu, May 3, 2018 at 12:21 PM, Magnus Ihse Bursie
wrote:
> On 2018-05-02 17:03, Volker Simonis wrote:
>>
>> Hi,
>>
>> we currently build OpenJDK and make it available from various sources
>> (e.g. GitHub, apt-get server, DockerHub). We also build the API
>> documentation (i.e. JavaDoc) and would
On 2018-05-02 17:03, Volker Simonis wrote:
Hi,
we currently build OpenJDK and make it available from various sources
(e.g. GitHub, apt-get server, DockerHub). We also build the API
documentation (i.e. JavaDoc) and would like to make it available from
our project page as well. However the default
Hi,
we currently build OpenJDK and make it available from various sources
(e.g. GitHub, apt-get server, DockerHub). We also build the API
documentation (i.e. JavaDoc) and would like to make it available from
our project page as well. However the default API doc produced by the
build looks as follo
