[
https://issues.apache.org/jira/browse/MNG-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731204#comment-17731204
]
Konrad Windszus commented on MNG-5697:
--------------------------------------
bq. Won't they be broken because they won't have the
<extension>true</extension> in the packaging plugin ? If they are broken, is
there any way we could mitigate that ?
One mitigation (only affecting ASF projects though):
https://github.com/apache/maven-apache-parent/pull/92, another more complete
but still WIP is https://github.com/apache/maven/pull/833.
> 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
> Fix For: 4.x / Backlog
>
>
> 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 of the build, before begin
> able to calculate the build plan*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
