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.
