MIME-Version: 1.0
References: 
 <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
 <CAASLQ4NU3BgfCnVxvAbu9vK9+gtPT87xX1uBj57b0y2J6nxi+Q@mail.gmail.com>
 <5F14C34E.4020704@anastigmatix.net> <5F14E15A.4040202@anastigmatix.net>
 <CAASLQ4PjzGVCj559r60Kw7i3uRUTzJraxBSDDsNtAt8v8_-oWQ@mail.gmail.com>
 <5F1664C5.2070700@anastigmatix.net>
 <CAASLQ4PeivyN6DkBPbgYTZmoqoOVdCDwinDFrREsXqZi2HQnWg@mail.gmail.com>
 <5F1735ED.6020707@anastigmatix.net>
 <CAASLQ4Off+PnB8FqKLokKjAkvKbW00=fjH_LxuYJOGp0_C1YAw@mail.gmail.com>
 <CAASLQ4PcU=P4ShuMJOEnQj6p7ZU0VcgJ9St6PMpXcNB_1jPQ+w@mail.gmail.com>
 <5F1753C9.4060500@anastigmatix.net>
 <CAASLQ4P_v7u5z76XWfPmVeBvQtNdraiN0MmsRRfq-eNh1O1aTA@mail.gmail.com>
 <5F175F40.1000905@anastigmatix.net>
 <CAASLQ4Ouw1hCHVtSC5XG7Fb-GoO0YAf4_PwsQc=22CvEzhQo6g@mail.gmail.com>
 <CAASLQ4MfBz2zj5gm-t+OX-8puxJvf8bSneKeUG+NuX=+CbYCLw@mail.gmail.com>
 <5F18C58F.8060204@anastigmatix.net>
 <CAASLQ4NkEDo-UAmqSwUTkCdMu+3WedKCfva5gzNTC45YcWEwNA@mail.gmail.com>
 <5F19C36C.70905@anastigmatix.net>
 <CAASLQ4M_f8cYmxfX5Jqgm9AJHsX62_Cc5pvniXjer4jAZOMOBQ@mail.gmail.com>
In-Reply-To: 
 <CAASLQ4M_f8cYmxfX5Jqgm9AJHsX62_Cc5pvniXjer4jAZOMOBQ@mail.gmail.com>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Sat, 25 Jul 2020 22:24:47 +0530
Message-ID: 
 <CAASLQ4Pcp24U3rkWkGvcidTfCLQEsAE1it7b3Sr_uNbgO3P9kA@mail.gmail.com>
Subject: Re: PL/Java new build plugin
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002bb51305ab46f3b3"
Precedence: bulk

--0000000000002bb51305ab46f3b3
Content-Type: text/plain; charset="UTF-8"

I have been going through the maven javadoc plugin's source. It is huge and
is over 6000 lines. Thankfully, most of it is customization things we can
avoid. I saw that the current configuration for maven javadoc has
exclude parameters in the pom.xml file. Now, maven uses a DirectoryScanner
to help out with the excludes which is available as a package in maven
shared utils. I am unable to think of a way to handle excludes with the
inbuilt Java APIs. Should I utilise DirectoryScanner or do you have any
other suggestions?

Regards,
Kartik.

>

--0000000000002bb51305ab46f3b3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I have been going through the maven javadoc plugin=
9;s source. It is huge and is over 6000 lines. Thankfully, most of it is cu=
stomization things we can avoid. I saw that the current configuration for m=
aven javadoc has exclude=C2=A0parameters in the pom.xml file. Now, maven us=
es a DirectoryScanner to help out with the excludes which is available as a=
 package in maven shared utils. I am unable to think of a way to handle exc=
ludes with the inbuilt Java APIs. Should I utilise DirectoryScanner or do y=
ou have any other suggestions?</div><div><br></div><div>Regards,</div><div>=
Kartik.</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">
</blockquote></div></div>

--0000000000002bb51305ab46f3b3--