ScriptingMojo Custom Packaging

>
> 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.
>

I have made these changes
https://github.com/amCap1712/pljava/commit/14045b10ca1428fc2914440a2220871ac7c9921b
but the build process fails with this error
https://gist.github.com/amCap1712/ad9fe94fd9fb6f4ff4f26913a464c226. I
checked the jar files manually to make sure the file is present in it. The
pgxs jar is also listed in the lists of url classpaths.