[
https://issues.apache.org/jira/browse/MDEP-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783028#comment-17783028
]
Karl Heinz Marbaise commented on MDEP-892:
------------------------------------------
Can you tell which versions of the maven-dependency-plugin you are exactly
using .. and JDK + Maven version.. unfortunately I can figure out that based on
the example project...
> go-offline does not correctly resolve overridden properties
> -----------------------------------------------------------
>
> Key: MDEP-892
> URL: https://issues.apache.org/jira/browse/MDEP-892
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Reporter: Arnout Engelen
> Priority: Minor
>
> When a project shares a parent pom with a dependency, and overrides a
> property of that parent pom, this is not picked up by
> {{{}dependency:go-offline{}}}.
> I have shared a reproducer at
> [https://codeberg.org/raboof/maven-property-resolution] . The scenario is
> `one` and `other-mod` both have parent pom `other-parent`. `other-parent`
> specifies version 7.4 of a dependency, but `one` overrides this to 7.3. Other
> plugins (including `mvn dependency:tree`) pick 7.3 in this scenario, but `mvn
> dependency:go-offline` downloads version 7.4.
> It seems [https://github.com/apache/maven-dependency-plugin/pull/2]
> (unmerged) fixed this, but its successor
> [https://github.com/apache/maven-dependency-plugin/pull/135] (unmerged) does
> not.
> An alternative is to use [https://github.com/qaware/go-offline-maven-plugin]
> instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
