[
https://issues.apache.org/jira/browse/MNG-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645831#comment-17645831
]
ASF GitHub Bot commented on MNG-7622:
-------------------------------------
michael-o commented on PR #907:
URL: https://github.com/apache/maven/pull/907#issuecomment-1345628665
> One addendum: "at the end it will replace the actual POM with the consumer
POM quite same as maven-shade-plugin"... a bit more: it intentionally use
`startsWith` for extension, as it not replaces _only the POM_ but all the
"whistle and bells" (signature, checksum, whatever) it may have more.... and
that _is the key_ thing here, and that enables today's m-gpg-p to function.
Then it would also replace `.pompom` which is not what you want, no? I guess
you want either exact `.pom` or starts with `.pom.`, on?
> Reimplement Consumer POM feature
> --------------------------------
>
> Key: MNG-7622
> URL: https://issues.apache.org/jira/browse/MNG-7622
> Project: Maven
> Issue Type: Task
> Components: build/consumer
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Current implementation relies on deprecated resolver API (is deprecated as it
> is OOM prone), and also renders use cases like m-gpg-p but also checksum-m-p
> broken.
> Reimplement consumer POM feature that:
> * does not use FileTransformer API
> * allows use cases like m-gpg-p
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
