[
https://issues.apache.org/jira/browse/MSHADE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Filip updated MSHADE-399:
--------------------------------
Environment:
maven 3.8.1
maven-shade-plugin 3.3.1-SNAPSHOT (I tested various version, 2.4.1, 3.1.1,
3.2.1, 3.2.4)
jdk 1.8
macos 11.4 / linux 5.2.9
was:
maven 3.8.1
maven-shade-plugin 3.3.1-SNAPSHOT (I tested various version, 2.4.1, 3.1.1,
3.2.1, 3.2.4)
> Infinite cycle with test dependency at different versions
> ---------------------------------------------------------
>
> Key: MSHADE-399
> URL: https://issues.apache.org/jira/browse/MSHADE-399
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 3.2.4
> Environment: maven 3.8.1
> maven-shade-plugin 3.3.1-SNAPSHOT (I tested various version, 2.4.1, 3.1.1,
> 3.2.1, 3.2.4)
> jdk 1.8
> macos 11.4 / linux 5.2.9
> Reporter: Stefan Filip
> Priority: Major
> Attachments: alpha-pom.xml, mvn-cycle.zip, pom.xml
>
>
> Hello,
> The Maven Shade plugin goes into an infinite loop when we specify a test
> dependency with the following properties:
> # the artifactId of the dependency is specified using properties
> # we have a parent that specified a different version of the dependency
> # the test dependency has dependencies of its own
> I attached the smallest repro that I could get in mvn-cycle.zip. `mvn clean
> install` will reproduce the issue.
> I debugged a bit but I don't understand exactly what the code is trying to do
> or the maven APIs that are called. The issue here looks to be that the
> project that is constructed at the reduced-pom phase. The project ends up
> having a the dependency list that contains both versions of test dependency
> and that invalidates the assumptions of the reduction loop.
> Let me know if you have questions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
