[
https://issues.apache.org/jira/browse/MNG-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003696#comment-17003696
]
Herve Boutemy commented on MNG-5697:
------------------------------------
yes, I'm sure this nice idea has issues.
Today, re-reading it, I now see one issue: ArtifactHandler is not about
packaging but about dependency type, then has a fully different target location.
But at least the part about splitting packagings' LifecycleMapping into each
"main" packaging plugin seems a good idea, if we ever have time to work on it...
> remove LifecycleMapping and ArtifactHandler from maven-core: move to target
> packaging plugin
> --------------------------------------------------------------------------------------------
>
> Key: MNG-5697
> URL: https://issues.apache.org/jira/browse/MNG-5697
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Robert Scholte
> Priority: Major
>
> 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
(v8.3.4#803005)
