Subject: Re: PL/Java new build plugin
To: Kartik Ohri <kartikohri13@gmail.com>
References: 
 <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
 <5F071CFC.9090306@anastigmatix.net>
 <CAASLQ4MLFd6zhoh+sWWz+iu4d8+H2ML+y=kL990k7H=kk74pvA@mail.gmail.com>
 <5F072647.50301@anastigmatix.net>
 <CAASLQ4Ms0QGf-Qh966HrsoaWzwf1SYHZ0WmZHApQePbcyPejCQ@mail.gmail.com>
 <CAASLQ4NFHYH1pfGJtCZDfdcxf_ZzLA+X+ko86vpyRDKVYr489Q@mail.gmail.com>
 <5F0734AD.7060001@anastigmatix.net>
 <CAASLQ4PDcaAJ8fEwXXFW6XPakc7GCNVgPNGCxA8KYMzPDZw4+w@mail.gmail.com>
 <5F077926.2050806@anastigmatix.net>
 <CAASLQ4OuFQCiSMeypQtfRaAvj-4H-EAgszLwdAo6Tc1zS9B66g@mail.gmail.com>
 <5F07C2D5.5050904@anastigmatix.net>
 <CAASLQ4PSizkzBKyyfkp9ccJ1qDPLRLu6g2bo9cN-XuTzGQFGfQ@mail.gmail.com>
 <CAASLQ4P9zGxHda=HAGJ2eAa-oMmJtnPm=4a14mj4P-QpfFsYxg@mail.gmail.com>
 <5F0D35BA.30904@anastigmatix.net>
 <CAASLQ4NmornyOW8n-qyneLpDVPgV0Js=+=Eys6bw3Y-ZiVbVjA@mail.gmail.com>
 <5F0DF1CA.805@anastigmatix.net>
 <CAASLQ4MZurpHu6zu7JV3Fo82RuhuJxugEfxAQOh0+SwsOmtkPQ@mail.gmail.com>
Cc: pljava-dev@lists.postgresql.org
From: Chapman Flack <chap@anastigmatix.net>
Message-ID: <5F0E1A50.80004@anastigmatix.net>
Date: Tue, 14 Jul 2020 16:49:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: 
 <CAASLQ4MZurpHu6zu7JV3Fo82RuhuJxugEfxAQOh0+SwsOmtkPQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 07/14/20 16:40, Kartik Ohri wrote:
> I looked into the maven-antrun-plugin. The relevant part is here
> <https://github.com/apache/maven-antrun-plugin/blob/8e5b3c613e96c20881347ec16813864a2d8ef0bb/src/main/java/org/apache/maven/plugins/antrun/AntRunMojo.java#L364>.
> It adds the classpaths as a reference to an instance of an Ant Project.

Right, because we have the extra indirection of Maven plugin, running Ant
task, running script. You'll be able to shorten that to just Maven plugin
running script, so the key might be looking in the Ant source to see what
the <script> task does with a classpath ref.

> I might be doing something wrong in the integration itself which might be a
> cause of this.

It's worth mentioning that the difficulty only results from the weird stuff
Maven does with classpaths. If you just write a standalone hello-world-style
Java program that uses the ScriptEngineManager, you should find that it
Just Works. (As long as you're in Java 14 or earlier; for 15 of course you'd
need the two Graal jars on the classpath.)

So that might be an easy way to reassure yourself that you haven't missed
something in how you're calling it.

Regards,
-Chap