maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MRESOLVER-9) DefaultDependencyCollector does not correctly handle dependency management
Date Sat, 08 Jun 2019 20:17:00 GMT

     [ https://issues.apache.org/jira/browse/MRESOLVER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov updated MRESOLVER-9:
-----------------------------------
    Description: During dependency processing the {{DependencySelector}} is called to decide
if a dependency is to be selected. The call to {{DependencySelector.selectDependency()}} is
performed with the unmanaged dependency, but needs to be performed with the managed dependency.
With the fix applied, the result no longer contains dependencies whose scope or optionality
has been managed to not be part of the result (correct behaviour). Without the fix applied,
the result contains dependencies with a managed scope or optionality not filtered out by the
{{DependencySelector}} in use (incorrect behaviour).  (was: During dependency processing the
'DependencySelector' is called to decide if a dependency is to be selected. The call to 'DependencySelector.selectDependency(
dependency )' is performed with the unmanagement dependency but needs to be performed with
the managed dependency. With the fix applied, the result no longer contains dependencies whose
scope or optionality has been managed to not be part of the result (correct behaviour). Without
the fix applied, the result contains dependencies with a managed scope or optionality not
filtered out by the 'DependencySelector' in use (incorrect behaviour).)

> DefaultDependencyCollector does not correctly handle dependency management
> --------------------------------------------------------------------------
>
>                 Key: MRESOLVER-9
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-9
>             Project: Maven Resolver
>          Issue Type: Bug
>            Reporter: Christian Schulte
>            Priority: Critical
>             Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> During dependency processing the {{DependencySelector}} is called to decide if a dependency
is to be selected. The call to {{DependencySelector.selectDependency()}} is performed with
the unmanaged dependency, but needs to be performed with the managed dependency. With the
fix applied, the result no longer contains dependencies whose scope or optionality has been
managed to not be part of the result (correct behaviour). Without the fix applied, the result
contains dependencies with a managed scope or optionality not filtered out by the {{DependencySelector}}
in use (incorrect behaviour).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message