[
https://issues.apache.org/jira/browse/NIFI-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFI-6272.
-------------------------------
Resolution: Fixed
> maven-dependency-tree v2.2 does not resolve dependencies in the same way the
> build does
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-6272
> URL: https://issues.apache.org/jira/browse/NIFI-6272
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: nifi-nar-maven-plugin-1.3.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: nifi-nar-maven-plugin-1.3.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The NiFi NAR Maven plugin 1.3.0 uses maven-dependency-tree version 2.2. When
> obtaining the dependency tree for a given artifact, it doesn't produce the
> same results that the build produces. For example, if a module has multiple
> transitive dependencies on the same module, say X v1 and X v2, Maven will
> decide to use v2 during the build, but the dependency tree returns both v1
> and v2. This is a problem because v1 may have never been downloaded locally
> since it wasn't going to be used.
> Upgrading to maven-dependency-tree version 3.0.1 produces a consistent result
> with the build and only returns the one transitive dependency in the result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
