You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2022/07/05 11:36:00 UTC
[jira] [Updated] (MNG-5697) remove LifecycleMapping and ArtifactHandler from maven-core: move to target packaging plugin
[ https://issues.apache.org/jira/browse/MNG-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MNG-5697:
-------------------------------
Description:
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*
was:
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
> 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 or the build, before begin able to calculate the build plan*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)