[
https://issues.apache.org/jira/browse/MNG-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739813#comment-17739813
]
Herve Boutemy edited comment on MNG-7832 at 7/4/23 6:41 AM:
------------------------------------------------------------
I understand the global idea: thanks Robert for the reminder
we still need to document precisely how this will be done by users consuming
dependencies (which is a different question to users building with a packaging)
and if it is not relatively transparent, I think some base artifact handlers
deserve staying in Maven core, like jar = THE basic java dependency
on moving less used artifact handlers from Jakarta EE land out of core into
custom artifact handlers, I have no doubt: in fact, in the past, our main issue
is that it has never been documented how to create a custom artifact handler
and how to consume it (same for custom packaging): AFAIK, we don't have any
documentation yet, we just have a better documentation of core ones.
I'm not against moving things out of core, but please let's do it in the right
order: document what creating and using custom artifact handlers mean. Then and
only then we can do the move (and again, I imagine we won't do the brutal move
for absolutely everything, as it is done currently without taking care of user
experience)
was (Author: hboutemy):
I understand the global idea: thanks Robert for the reminder
we still need to document precisely how this will be done by users consuming
dependencies (which is a different question to users building with a packaging)
and if it is not relatively transparent, I think some base artifact handlers
deserve staying in Maven core, like jar = THE basic java dependency
on moving less used artifact handlers from Jakarta EE land out of core into
custom artifact handlers, I have no doubt: in fact, in the past, our main issue
is that it has never been documented how to create a custom artifact handler
and how to consume it (same for custom packaging): AFAIK, we don't have any
documentation yet, we just have a better documentation of core ones. I'm not
against moving things out of core, but please do let's do it in the right
order: document what creating and using custom ones mean. Then and only then we
can do the move (and again, I imagine we won't do the brutal move for
absolutely everything, as it is done currently without taking care of user
experience)
> revert artifact handlers move to plugins
> ----------------------------------------
>
> Key: MNG-7832
> URL: https://issues.apache.org/jira/browse/MNG-7832
> Project: Maven
> Issue Type: Sub-task
> Components: Dependencies, Plugins and Lifecycle
> Reporter: Herve Boutemy
> Priority: Major
>
> 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 artifact
> 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 message was sent by Atlassian Jira
(v8.20.10#820010)
