Skip to content

[MRESOLVER-8] ScopeDependencySelector incorrectly de-selects direct dependencies #770

@jira-importer

Description

@jira-importer

Christian Schulte opened MRESOLVER-8 and commented

The ScopeDependencySelector decides if a node is a direct dependency or transitive dependency differently based on the request performed. For the CollectRequest.setRootArtifact(Artifact) case, the class is working correctly. For the CollectRequest.setRoot(Dependency) case, the class is de-selecting direct dependencies instead of transitive dependencies.


Issue Links:

  • MNG-6135 Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
    ("blocks")

  • MPLUGIN-321 improve documentation on maven-plugin-annotations telling that optional=true is sufficient

  • MEAR-246 Upgrade the EAR lifecycle to use the maven-resources-plugin 3.0.2.
    ("breaks")

  • MPLUGIN-296 java.lang.ClassNotFoundException: org.apache.maven.plugins.annotations.Execute
    ("breaks")

  • MWAR-400 Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2
    ("breaks")

  • MRESOURCES-234 Upgrade of commons-io to 2.5 and correction of invalid scope.
    ("breaks")

  • MPMD-230 Required class missing: org/apache/commons/io/IOUtils
    ("breaks")

  • MRESOLVER-12 Addition of unit tests for DependencySelector implementations
    ("is depended upon by")

Remote Links:

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority:criticalCrashes, loss of data, severe memory leak

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions