public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chapman Flack <[email protected]>
To: Kartik Ohri <[email protected]>
Cc: [email protected]
Subject: Re: PL/Java new build plugin
Date: Sat, 25 Jul 2020 15:10:01 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAASLQ4P+YVjp6cQY7OyDEx+0dOCnEbDWkxN+WJ13MWMg5wxCyw@mail.gmail.com>
References: <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
<[email protected]>
<CAASLQ4PeivyN6DkBPbgYTZmoqoOVdCDwinDFrREsXqZi2HQnWg@mail.gmail.com>
<[email protected]>
<CAASLQ4Off+PnB8FqKLokKjAkvKbW00=fjH_LxuYJOGp0_C1YAw@mail.gmail.com>
<CAASLQ4PcU=P4ShuMJOEnQj6p7ZU0VcgJ9St6PMpXcNB_1jPQ+w@mail.gmail.com>
<[email protected]>
<CAASLQ4P_v7u5z76XWfPmVeBvQtNdraiN0MmsRRfq-eNh1O1aTA@mail.gmail.com>
<[email protected]>
<CAASLQ4Ouw1hCHVtSC5XG7Fb-GoO0YAf4_PwsQc=22CvEzhQo6g@mail.gmail.com>
<CAASLQ4MfBz2zj5gm-t+OX-8puxJvf8bSneKeUG+NuX=+CbYCLw@mail.gmail.com>
<[email protected]>
<CAASLQ4NkEDo-UAmqSwUTkCdMu+3WedKCfva5gzNTC45YcWEwNA@mail.gmail.com>
<[email protected]>
<CAASLQ4M_f8cYmxfX5Jqgm9AJHsX62_Cc5pvniXjer4jAZOMOBQ@mail.gmail.com>
<[email protected]>
<CAASLQ4P+YVjp6cQY7OyDEx+0dOCnEbDWkxN+WJ13MWMg5wxCyw@mail.gmail.com>
On 07/25/20 14:05, Kartik Ohri wrote:
> Also, I am trying to run the javadoc tool directly to know how it works but
> am getting some errors. Can you tell me the command I should execute to
> build the docs successfully? I looked up online for tutorials but most
> predate Java 9 and the module system so are not of much help.
I think you can get a basic set of javadocs for the pljava-api subproject,
for example, if you run something like
javadoc \
--module org.postgresql.pljava \
--module-source-path org.postgresql.pljava=pljava-api/src/main/java \
-d /tmp/put-them-here
You can find out what options the maven-javadoc-plugin is using by
adding <debug>true</debug> in its configuration, then running mvn site.
With <debug>, it will leave behind files javadoc.sh, options, argfile
in the apidocs directory. Then you can just see how many options the
plugin put in can be thrown away and it still works.
Of course we'll want some of the options that control what access
levels to show, page headers and footers, that kind of stuff. It's
just that all the lengths the maven plugin goes to trying to micromanage
where javadoc finds the files to document are nothing but trouble.
If you tell it what module to document and where to find it, really,
javadoc can figure out the rest.
I wouldn't mind writing the scripty bits to run javadoc, once there is
a scriptable mojo I can use to do it. Or if you'd like to, that's cool.
Regards,
-Chap
view thread (132+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PL/Java new build plugin
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox