| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
| Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PL/Java new build plugin |
| Date: | 2020-07-20 00:12:10 |
| Message-ID: | 5F14E15A.4040202@anastigmatix.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pljava-dev |
On 07/19/20 18:03, Chapman Flack wrote:
> To test with Graal, you can (1) do a build with Java 15 and see that
> it breaks because Nashorn is gone :), and then (2) merge the
> chore/master/denashorn branch and edit the main (parent) pom.xml, and
> change the nashorngone profile so the two graal jars are added as
> dependencies of org.postgresql:pljava-pgxs instead of maven-antrun-plugin.
I meant to ask also: is it possible for the plugin configuration's
<script> tag to allow attributes, such as
<script mimetype="application/javascript">
...
</script>
or
<script engine="nashorn">...</script>
I have noticed that Maven configurations tend not to use attributes
much, and instead make everything its own element, like
<scriptLanguage>nashorn</scriptLanguage>
<script>...</script>
but I have not checked whether Maven is actually incapable of using
attributes in configs, or that has just been a common style among
existing plugins.
I would find the style with an attribute to be more compact and
clear.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kartik Ohri | 2020-07-21 02:51:43 | Re: PL/Java new build plugin |
| Previous Message | Chapman Flack | 2020-07-19 22:03:58 | Re: PL/Java new build plugin |