apache / apache/maven

[MNG-7832] revert artifact handlers move to plugins

Open
#9,086 4 comments 0 reactions 1 assignee Claimed by @hboutemy View on GitHub
priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
20h 42m
Merged PRs (30d)
297

Description

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** opened **[MNG-7832](https://issues.apache.org/jira/browse/MNG-7832?redirect=false)** and commented

MNG-5697 proposed to move at the same time packaging mapping AND artifact handlers to packaging-oriented plugins

packaging mapping is feasible, and can make sense: user configures a packaging plugin in his pom.xml to benefit from the full associated build lifecycle, why not

but attifact handler is completely another beast: it's about consuming an artifact as a dependency, then not lead at all by the packaging of the project consuming the artifacts as dependencies https://maven.apache.org/ref/3.9.3/maven-core/artifact-handlers.html

we need to split the 2 aspects:
1. finish lifecycle mapping definition to plugins, and remove at the end the definition from core, while learning users how to not any more benefit from implicit core definition

2. revert artifact handlers copy to packaging plugins, because they create confusion: artifacts will never be consumed with an artifact handler defined by an associated packaging plugin

once someone finds something reasonable about artifact handlers, we can implement it later

---

This issue is a sub-task of [MNG-5697](https://issues.apache.org/jira/browse/MNG-5697)

**Issue Links:**
- [MNG-8472](https://issues.apache.org/jira/browse/MNG-8472) Sort out the problem about packaging in Maven 4
(_**"causes"**_)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.