[ 
https://issues.apache.org/jira/browse/MNG-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731167#comment-17731167
 ] 

Herve Boutemy edited comment on MNG-5697 at 6/10/23 6:50 AM:
-------------------------------------------------------------

existing projects will require:
1. to have plugins as extension
2. to have plugins as plugins, and not only pluginManagement

on the good sides, error message when packaging is missing is really clear:
{noformat}
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unknown packaging: bundle @ line 27, column 16{noformat}
In addition: I can understand that we want to remove Jakarta EE packaging 
definition from core (war, ear, rar, ...) and Maven Plugin,

but removing jar packaging (and even more its many artifact handlers that are 
constantly used) from core looks a very bad idea


was (Author: hboutemy):
existing projects will require:
1. to have plugins as extension
2. to have plugins as plugins, and not only pluginManagement

on the good sides, error message when packaging is missing is really clear:
{noformat}
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unknown packaging: bundle @ line 27, column 16{noformat}
In addition: I can understand that we want to remove Jakarta EE packaging 
definition from core (war, ear, rar, ...) and Maven Plugin,

but removing jar packaging from core looks a very bad idea

> 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)

Reply via email to