On 11 March 2010 16:49, Phil Housley <[email protected]> wrote:
> Hi,
>
> I am (yet again) trying to subvert Maven with a custom plugin and
> finding that the special cases in the core are causing problems. What
> I'm aiming for is the ability to have a project which combines a
> couple of modules as a single "release", and then deploys their
> artifacts together, along with some metafiles. The modules also have
> custom packaging types, and the deployment means a custom process over
> some webservices.
>
> The issue is that only pom package projects are allowed to have
> modules, and the pom lifecycle includes the standard install and
> deploy plugin, which will fail as there is no distributionManagement
> section. Is it possible to either completely inhibit the plugins in
> the pom lifecycle, or to create another packaging type which allows
> multi-module?
To partly answer my own question, it seems that the checks for multi
module and parent allowed are coded as simply if
("pom".equals(project.getPackaging()), so it doesn't look like I can
use another packaging type there. I'm still looking into a way to get
the install and deploy plugins out of the pom lifecycle, but without
too much hope. I guess I will have to resort to specifying a specific
goal and ignoring the lifecycle altogether...
> Any thoughts much appreciated.
>
> Thanks,
>
> --
> Phil Housley
>
--
Phil Housley
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
