From: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
Subject: | Re: PL/Java new build plugin |
Date: | 2020-07-22 02:19:05 |
Message-ID: | CAASLQ4P=0g_PKcP9B82xFSJzAnSDzu6kVNJkM_b3HqbcYqznhw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
On Wed, Jul 22, 2020 at 4:00 AM Chapman Flack <chap(at)anastigmatix(dot)net> wrote:
> On 07/21/20 14:55, Kartik Ohri wrote:
> > I had already come across your answer in my search and figured that you
> > might have forgotten about it :). I have seen antrun's source. I
> initially
> > wanted to have something like it but was unable to figure out how
> > antrun does that.
>
> That made me curious, so I took your plugin branch and just gave the
> 'script' parameter the type PlexusConfiguration, and it did pretty much
> what I thought antrun was doing. Nothing up my sleeve. :)
>
https://github.com/jcflack/pljava/commits/PlexusConfig
>
> One less dark magical secret. So, this means that Maven looks
for @Parameter annotated variables and matches them to xml dom elements.
And the supertype for maven plugin parameter type matching is
PlexusConfiguration (or something it inherits).
Is it possible that the test condition for "your engine doesn't support
> your mimetype" could be backwards?
To be sure, you mean the mimetype should be preferred over engine ?
Regards,
Kartik.
From | Date | Subject | |
---|---|---|---|
Next Message | Kartik Ohri | 2020-07-22 02:25:38 | Re: PL/Java new build plugin |
Previous Message | Chapman Flack | 2020-07-21 22:30:15 | Re: PL/Java new build plugin |