[
https://jira.codehaus.org/browse/MNG-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360559#comment-360559
]
Robert Scholte commented on MNG-5697:
-------------------------------------
MDEPLOY-71 describes an important issue related to this. Right now it s
impossible to do a {{deploy:deploy-file}} of a custom packaging type without
having a pom + extensions. In our solution we need to solve this as well.
> remove LifecycleMapping and ArtifactHandler from maven-core: move to target
> packaging plugin
> --------------------------------------------------------------------------------------------
>
> Key: MNG-5697
> URL: https://jira.codehaus.org/browse/MNG-5697
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Robert Scholte
>
> Maven Core should only be aware of the pom packaging details, the rest of the
> {{ArtifactHandlers}} and {{LifecycleMappings}} should be moved to their own
> packaging plugin:
> - jar packaging: maven-jar-plugin
> - ejb and ejb3 packagings: maven-ejb-plugin
> - maven-plugin packaging: maven-plugin-plugin
> - war packaging: maven-war-plugin
> - ear packaging: maven-ear-plugin
> - rar packaging: maven-rar-plugin
> - par packaging: ?
> {{LifecycleMappings}}
> http://maven.apache.org/ref/3.2.5/maven-core/default-bindings.html
> {{ArtifactHandlers}}
> http://maven.apache.org/ref/3.2.5/maven-core/artifact-handlers.html
> Maven core should then get the lifecycle mappings and artifact handlers
> configurations from the plugin at the beginning or the build, before begin
> able to calculate the build plan
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
