| 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: the ReportScriptingMojo |
| Date: | 2020-08-19 14:54:38 |
| Message-ID: | 5F3D3D2E.4070109@anastigmatix.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pljava-dev |
On 08/19/20 10:43, Chapman Flack wrote:
> ...META-INF/plexus/components.xml
I think my inclination would be to supply such a file with the role-hint
of 'pgxs', and mapping every phase to empty. Then what the plugin does will
be completely determined by what script <execution>s you configure, and
what phases you put them in.
Then the packaging type of pljava-so could be pgxs, and you would simply
specify the <phase> for each <execution> in the pom (as is already done
for the set-properties execution). So, what the plugin does will be
completely determined by what script <execution>s you configure, and
what phases you put them in.
I think I would also change ScriptingMojo to declare COMPILE as its
default phase. The set-properties execution would still specify
initialize as its phase, as it does now, but I think the usual
behavior is if a phase isn't specified, it will be compile.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2020-08-19 15:22:37 | Re: the ScriptingMojo |
| Previous Message | Chapman Flack | 2020-08-19 14:43:01 | Re: the ReportScriptingMojo |