You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Anton Tanasenko <at...@gmail.com> on 2015/04/20 00:22:29 UTC
Custom packaging types: configuring DefaultLifecycleMapping mojo executions
Hi,
There is no possibility right now to map goals to phases with a custom
configuration and/or dependencies when dealing with custom packagin types.
DefaultLifecycleMapping only has 'goals' parameter in components.xml, and
DefaultLifecyclePluginAnalyzer does not take those into account.
I propose an enhancement, which adds support for setting configuration and
dependencies as part of custom packaging type mojo executions.
A usecase is an ability to create a packaging type which mostly consists of
standard maven plugins but with a custom configuration.
Example: package phase made up of antrun and assembly which require certain
dependencies (ant-contrib, assembly descriptor bundle) and must also be
configured to be used.
I have created a jira issue: https://issues.apache.org/jira/browse/MNG-5805
Note that this currently would not work out of the box because sisu-plexus
does not support Xpp3Dom typed bean properties, so I've created a separate
issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=464959
--
Regards,
Anton.
Re: Custom packaging types: configuring DefaultLifecycleMapping mojo executions
Posted by Jason van Zyl <ja...@takari.io>.
+1
This will be a nice feature addition.
On Apr 19, 2015, at 6:22 PM, Anton Tanasenko <at...@gmail.com> wrote:
> Hi,
> There is no possibility right now to map goals to phases with a custom
> configuration and/or dependencies when dealing with custom packagin types.
> DefaultLifecycleMapping only has 'goals' parameter in components.xml, and
> DefaultLifecyclePluginAnalyzer does not take those into account.
>
> I propose an enhancement, which adds support for setting configuration and
> dependencies as part of custom packaging type mojo executions.
>
> A usecase is an ability to create a packaging type which mostly consists of
> standard maven plugins but with a custom configuration.
> Example: package phase made up of antrun and assembly which require certain
> dependencies (ant-contrib, assembly descriptor bundle) and must also be
> configured to be used.
>
> I have created a jira issue: https://issues.apache.org/jira/browse/MNG-5805
>
> Note that this currently would not work out of the box because sisu-plexus
> does not support Xpp3Dom typed bean properties, so I've created a separate
> issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=464959
>
> --
> Regards,
> Anton.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org