[
https://issues.apache.org/jira/browse/MSHADE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509907#comment-17509907
]
Robert Stupp commented on MSHADE-413:
-------------------------------------
Reproducer from projectnessie:
# {{git clone https://github.com/projectnessie/nessie.git}}
# {{git checkout a8572ea368e03f5cb5e805b2af1776556a62f2ed}}
# {{mvn clean install -T1C -DskipTests}}
# {{mvn clean install -T1C -pl clients/spark-extensions -pl
clients/spark-3.2-extensions}} (if the above doesn't run into the endless loop)
# With the workaround @ {{git checkout
25e2b891f2ea4e032bf188574002517f583c7645}}, the last {{mvn}} passes fine
> Maven share plugin enters endless loop
> ---------------------------------------
>
> Key: MSHADE-413
> URL: https://issues.apache.org/jira/browse/MSHADE-413
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 3.2.4
> Reporter: Robert Stupp
> Priority: Critical
>
> {{ShadeMojo.createDependencyReducedPom()}} pulls in {{origDeps =
> project.getDependencies()}} and later modifies these {{Dependency}} objects.
> This leads to a
> [reproducible|https://github.com/projectnessie/nessie/issues/3678] endless
> loop (see below).
> If the Shade plugin's not using the {{Dependency}} objects "owned by Maven
> itself" (by setting {{promoteTransitiveDependencies}} to {{true}}), the build
> passes fine.
> I think, _modifying_ the {{Dependency}} objects "owned by Maven itself" is
> bad for two reasons (which IMO justify the increased priority of this
> ticket):
> # the reproducible endless loop
> # it breaks the correctness of the project build - at least plugins running
> after the {{shade}} goal that use those dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
